Service-oriented architecture is the entry point to modern application architectures. Yet conceptual, design and execution mistakes derail many organizations' SOA efforts. Here, we list the most common SOA pitfalls and corrective actions for application leaders responsible for architecture.
- Organizational: Define Clear Objectives and Take an Incremental Approach to SOA Adoption
- Failing to Define Goals and Success Criteria
- Taking a "Big Bang" Approach
- Failing to Address Cultural Concerns
- Conceptual: Apply Different Types of SOA, as Appropriate
- Thinking You Can Buy SOA
- Thinking SOA and APIs Are Different
- Thinking SOA and Microservices Are Different
- Implementation: Choose Patterns That Ensure Flexibility and Usability
- Using Canonical Models
- Being Service-Centric Rather Than Consumer-Centric
- Overlooking Event-Driven Patterns
Gartner Recommended Reading
©2020 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.