Summary of Why You Should Be Talking About Microservices

Looking for the article?
We have the summary! Get the key insights in just 5 minutes.

Why You Should Be Talking About Microservices summary

Editorial Rating



  • Applicable
  • Overview
  • For Beginners


As organizations strive for greater agility, their software development teams often turn to microservices for flexibility and efficiency. Amazon, PayPal and Netflix, among many tech supergiants, have been leaving their monolithic structures behind and are moving to microservices architectures. For executives looking toward their own transition, a team at the Boston Consulting Group offers a clear, authoritative introduction to the technology.

About the Authors

Neveen Awad is a managing director and partner at Boston Consulting Group, and Stuart Scantlebury is a senior advisor. Firas Sleiman is an associate director and architecture practice lead at BCG Platinion.


Microservices consist of small, self-contained, reusable blocks of code.

Each microservice performs a specific service and has all the resources – code, data (or access to data) and interfaces – that it needs to execute its task. Developers communicate with the microservice via an application programming interface (API), which liberates them from having to know anything about the microservice’s internal functioning, such as its programming language or software logic.

A microservices architecture loosely couples microservices – including backup components in case of failure – with automation tools, thus providing a resilient structure.

Microservices enhance the development process and facilitate continual...

Comment on this summary

More on this topic

Expanding AI’s Impact with Organizational Learning
Agile Is Not Enough
Six Simple Steps Pave the Way to the Cloud
Developing a Digital Mindset for L&D
Migration to Innovation
The Service Factory of the Future

Related Channels