Service Fabric implements eShop On Containers, eshopcontainers

Service Fabric implements eShop On Containers, eshopcontainers
From Pet Shop to eShop on Container, Microsoft presents the technology evolution path to developers. the Sample project of Net's development and architecture capabilities, Petshop is more about displaying the layered architecture of applications, design abstraction and communication between modules. EShop on Container focuses more on Architecture Design and microservices. Let's take a look at the architecture diagram of eshop on Container.

In, we can see that the backend service is divided

1 Identity microservice (Authentication Service)

2 Catalog microservice)

3 Ordering microservice)

4 Basket microservice (Shopping Cart Service)

5. Marketing microservice)

6 Locations microservice (geographic location information service)

In the previous layered architecture, these services are usually embodied in a certain module. Why should they be split into various services now? When we look at these services from the business scenario, we will find that the access peak time interval and capacity planning of each service are different, even the most convenient and simple technology stack for implementing these services may be different (of course powerful. net core is omnipotent, but the technical reserves of different online businesses in the company are different, it is possible to choose different technical implementation ). This is because if we integrate these modules into a program or service, we will encounter difficulties in expanding the system capacity during service peaks in different time periods, or lack of resources, or excessive resources. For example, you logged on to the system half an hour before the start of the flash sales business. The busiest part of the system was the logon module. When the flash sales started, the busiest part of the system was the order module. If the microservice architecture is not used, resources that are prepared for the login module half an hour ago may not be promptly released to the order module. If both modules use a single program architecture, it is likely that all resources are occupied by the flash sales business, and other user resources that normally access the system are occupied, cause system crash. With regard to Dev/Ops, developers and architects need to consider the impact of the hardware architecture layer on application.