Benefits and drawbacks of Microservices applications compared to Monolithic applications

Benefits and drawbacks of Microservices applications compared to Monolithic applications

• Amazon – Amazon is known as an Internet retail giant, but it did not start that way.
• In the early 2000s, Amazon’s retail website behaved like a single monolithic application.
• Due to the tight-connections between—and within—the multi-tired services, developers had to carefully untangle dependencies every time they wanted to upgrade or scale Amazon’s systems. This is one of the major drawback of monolithic application.
• It was painstaking process that cost plenty of money and required time to adjust.
• In 2001, due to development delays, coding challenges and service interdependencies faced with the need to refactor its system from scratch.
• Amazon broke it’s monolithic application into small independently running, service-specific applications.
• Amazon assigned ownership of each independent service to a team of developers, so that they could resolve the challenges more efficiently.
• Amazon “service-oriented architecture” was largely the beginning of what we now call microservices. Which leads to Amazon developing a number of solutions to support micaroservices architecture – such as Amazon AWS and Apollo — which it currently sells to enterprises throughout the world.
• Without its transition to microservices, Amazon could not have grown to become the most valuable company in the world — valued by market cap at $1.6 trillion as of August 1,2022.
• Similar way Netflix and Uber also moved to Microservices from monolithic architecture.

Benefits and Challenges of Microservices

Benefits	Challenges
Agility - it's easier to manage bug fixes and feature releases.	Complexity - Each service is simpler, but the entire system as a whole is more complex.
Small, focused teams - Small team sizes promote greater agility	Development and testing – It can be difficult when the application is evolving quickly.
Small code base – It’s easier to add new features.	Lack of governance – Due to so many different languages and frameworks the application becomes hard to maintain.
Mix of technologies - Teams can pick any technology that best fits the service.	Network congestion and latency - The use of many small, granular services can result in more inter-service communication.
Fault isolation -It won't disrupt the entire application even if one microservice is not working.	Management - To be successful with microservices requires a mature DevOps culture.
Scalability -  Services can be scaled independently, without scaling out the entire application.	Versioning. Multiple services could be updated at any given time, so need to design carefully.

Download 468.86 Kb.

Share with your friends: