Additional resources •
eShopOnContainers GitHub repo. Source code for the reference application https://aka.ms/eShopOnContainers/
Benefits of a microservice-based solution A microservice-based solution like this has many benefits:
Each microservice is relatively small — easy to manage and evolve . Specifically:
•
It is easy for a developer to understand and get started quickly with good productivity.
•
Containers start fast, which makes developers more productive.
•
An IDE like Visual Studio can load smaller projects fast, making developers productive.
•
Each microservice can be designed, developed, and deployed independently of other
microservices, which provide agility because it is easier to deploy new versions of microservices
frequently.
It is possible to scale out individual areas of the application . For instance, the catalog service or
the basket service might need to be scaled out, but not the ordering process. A microservices
infrastructure will be much more efficient with regard to the resources used when scaling out than a
monolithic architecture would be.
You can divide the development work between multiple teams . Each service can be owned by a
single development team. Each team can manage, develop, deploy, and scale their service
independently of the rest of the teams.
Issues are more isolated . If there is an issue in one service, only that service is initially impacted
(except when the wrong design is used, with direct dependencies between microservices), and other
services can continue to handle requests. In contrast, one malfunctioning component in a monolithic
98
CHAPTER 5 | Designing and Developing Multi-Container and Microservice-Based .NET Applications
deployment architecture can bring down the entire system, especially when it involves resources, such
as a memory leak. Additionally, when an issue in a microservice is resolved, you can deploy just the
affected microservice without impacting the rest of the application.
