How dotnet-architecture/eshoponazure works
Main Components
• Microservice Containers – Represent each autonomous backend service such as Basket.API, Catalog.API, Identity.API, and Ordering.API. Include additional specialized building blocks (e.g., Event Bus, Health Checks, Resilience libraries) from the “src/BuildingBlocks” folder.
• Integration/Event Communication – Emphasize the Integration Events and the Event Bus (e.g., RabbitMQ integration packages and the integration event log from the Catalog and Basket services) which provide asynchronous, cross-service communication.
• Docker/Deployment Components – Include elements for Docker Compose setups (docker-compose.yml and various override files) as well as different CLI tools to build and deploy the containers.
Relationships and Data Flows
• Event Bus as a central intermediary connecting microservices that rely on integration events.
Architectural Patterns and Design Principles
• Microservice segregation: Each service is designed to be autonomous, owns its own database and data model (evidenced from the separate folders and project files for each API).
• Domain-Driven Design (DDD) and CQRS elements: Some services especially in Ordering show commands, domain events, and repositories, which signifies the use of layering and command/handler patterns.
• Containerization: The deployment is based on Docker containers (with distinct Dockerfiles for Linux and Windows) – mark these boundaries clearly.
• Client-Server separation: Emphasize the clear separation between back-end (microservices) and the variety of client applications.
Technologies & Tools
• .NET Core for API services, ASP.NET Core MVC for web apps.
• Angular 2+ for SPA.
• Xamarin for mobile clients.
• Docker and Docker Compose (illustrated by multiple docker-compose files).
• RabbitMQ and Redis as key infrastructure components.
• Visual Studio solutions (such as eShopOnContainers.sln and specific mobile/web solution files) which allow toggling between different client/server projects.