skip to main content
Close Icon We use cookies to improve your website experience.  To learn about our use of cookies and how you can manage your cookie settings, please see our Cookie Policy.  By continuing to use the website, you consent to our use of cookies.
Global Search Configuration


The issue for developers at large with their many different needs and concerns is knowing when to turn to microservices and when to stay with traditional software architectures.


  • The monolithic application has a long history and still serves many useful functions.

Features and Benefits

  • Analyze the pros and cons of monolithic versus microservices against a table of criteria.
  • Identify the technology most appropriate for your software application requirements in terms of monoliths and microservices.

Key questions answered

  • Which software architecture is the right choice and what are the criteria?
  • How can FaaS offer a third option?

Table of contents


  • Catalyst
  • Ovum view
  • Key messages
  • Recommendations for enterprises
  • Recommendations for vendors

Architecture selection guidelines

  • Evolution of microservices
  • Key use cases for selecting monolithic architecture
  • Key use cases for selecting microservices architecture
  • Key criteria for selecting the right architecture for the task
  • When to break the monolith: microservices transformation

Scale, complexity, and development cost

  • The threshold when microservices win over monoliths

FaaS: a third option between microservices and monoliths

  • FaaS solutions are now available open source and portable


  • Further Reading
  • Author

Recommended Articles


Have any questions? Speak to a Specialist

Europe, Middle East & Africa team: +44 7771 980316

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

US team: +1 212-652-5335

Email us at

You can also contact your named/allocated Client Services Executive using their direct dial.
PR enquiries - Email us at

Contact marketing -

Already an Ovum client? Login to the Knowledge Center now