skip to main content
Close Icon

In order to deliver a personalized, responsive service and to improve the site, we remember and store information about how you use it. This is done using simple text files called cookies which sit on your computer. By continuing to use this site and access its features, you are consenting to our use of cookies. To find out more about the way Informa uses cookies please go to our Cookie Policy page.

Global Search Configuration


Contrary to popular belief, microservices architecture (MSA) does not necessarily offer a simpler approach to service-oriented architecture (SOA).


  • The proposition of having "smart endpoints and dumb pipes" implies implementation of microservices without an intelligent middleware layer.
  • MSA is an enterprise service bus (ESB) anti-pattern.

Features and Benefits

  • Understand how a microservices architectural approach results in significant operational overhead.
  • Gain insights into how API management simplifies microservice orchestration and management.

Key questions answered

  • What are the differences between SOA and a microservices architectural approach?
  • What are the key capabilities required for microservice orchestration and management?

Table of contents

Ovum view

  • Summary
  • Microservices architectural approach results in significant operational overhead
  • API management helps tackle challenges associated with microservices-based applications


  • Author

Recommended Articles


Have any questions? Speak to a Specialist

Europe, Middle East & Africa team - +44 (0) 207 017 7700

Asia-Pacific team - +61 (0)3 960 16700

US team - +1 646 957 8878

+44 (0) 207 551 9047 - Operational from 09.00 - 17.00 UK time

You can also contact your named/allocated Client Services Executive using their direct dial.
PR enquiries - Call us at +44 7770704398 or email us at

Contact marketing -

Already an Ovum client? Login to the Knowledge Center now