Gartner Research

Q&A on SOA and Latency in Applications

Published: 21 May 2009

ID: G00167611

Analyst(s): Jess Thompson

Summary

An application has service-oriented architecture when it employs five fundamental principles. It is the implementation choices, not the five principles of SOA, that result in an application having unacceptable latency.

Table Of Contents
  • Does Service-Oriented Architecture (SOA) Introduce Latency Into Applications?
  • Case 1: Using the Wrong Flow Management Technology
  • Case 2: Using Infrastructure Deployed for a Different Project Without Testing It
  • Case 3: Not Thoroughly Investigating Long-Term Requirements
  • Conclusion

©2019 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates. This publication may not be reproduced or distributed in any form without Gartner’s prior written permission. It consists of the opinions of Gartner’s research organization, which should not be construed as statements of fact. While the information contained in this publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner research may address legal and financial issues, Gartner does not provide legal or investment advice and its research should not be construed or used as such. Your access and use of this publication are governed by Gartner’s Usage Policy. Gartner prides itself on its reputation for independence and objectivity. Its research is produced independently by its research organization without input or influence from any third party. For further information, see Guiding Principles on Independence and Objectivity.

Already have a Gartner Account?

Purchase this Document

To purchase this document, you will need to register or sign in above

Become a client

Learn how to access this content as a Gartner client.