Skip to content
Permalink
main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
 
 
Cannot retrieve contributors at this time

6002CEM_XinTan

Since the focus of the eShopOnDapr reference app is on Dapr, the architecture of the app includes: Front-end web applications written in Blazor. It sends user requests to the API Gateway microservice. API Gateway abstracts the backend core microservices from the front-end client. It is implemented using Envoy, a high-performance, open-source service proxy. Envoy routes incoming requests to various backend microservices. Most requests are simple CRUD operations (e.g., getting a list of brands from a catalog) and are handled by making direct calls to the backend microservice. Other requests are logically more complex and require multiple microservices to work together. For these cases, eShopOnDapr implements an aggregator microservice that orchestrates workflows across the microservices required to complete the operation. The core back-end set of microservices includes the functionality required for an e-commerce store. Each is independent and independent of the others. Following a widely accepted domain decomposition pattern, each microservice isolates a specific business function: The Shopping Basket service manages the customer's shopping basket experience. Catalog services manage product items that are available for sale. Identity Services manages authentication and identity. The Subscription Service handles all aspects of placing orders and managing orders. Payment services process payments from customers. Finally, Event Bus supports asynchronous pub/sub messaging across microservices. Developers can plug in any of the Dapr-supported message brokers.