f4cio/eshoponcontainers

Purpose and entry points

This is a containerized .NET e-commerce reference system built as independently deployable services, client-facing web apps, and API gateways. Local composition starts from SourceCode/eShopOnContainers/src/docker-compose.yml; Kubernetes rollout is orchestrated by SourceCode/eShopOnContainers/deploy/k8s/helm/deploy-all.sh. Each service/app is an ASP.NET Core entry point via its Program.cs, for example SourceCode/eShopOnContainers/src/Services/Ordering/Ordering.API/Program.cs.

Client and edge layer

MVC and Angular SPA clients provide catalog, basket, and order experiences; they authenticate against the identity service and call backend APIs through web-oriented BFF aggregation/gateway layers.

• MVC: SourceCode/eShopOnContainers/src/Web/WebMVC/Program.cs, SourceCode/eShopOnContainers/src/Web/WebMVC/Services/OrderingService.cs

• SPA host/client: SourceCode/eShopOnContainers/src/Web/WebSPA/Program.cs, SourceCode/eShopOnContainers/src/Web/WebSPA/Client/src/modules/app.module.ts

• Web/mobile shopping aggregators combine basket, catalog, and ordering calls, including gRPC clients: SourceCode/eShopOnContainers/src/ApiGateways/Web.Bff.Shopping/aggregator/Program.cs, SourceCode/eShopOnContainers/src/ApiGateways/Mobile.Bff.Shopping/aggregator/Services/OrderingService.cs

• Kubernetes API-gateway deployments use Envoy configuration: SourceCode/eShopOnContainers/deploy/k8s/helm/apigwws/envoy.yaml.

Core commerce services

Catalog owns product data, images, stock handling, and product-price events. Basket owns per-user carts in Redis and emits checkout events. Ordering is the principal workflow boundary, with DDD aggregates, command/query separation, transactions, and idempotent requests.

• Catalog: SourceCode/eShopOnContainers/src/Services/Catalog/Catalog.API/Controllers/CatalogController.cs, SourceCode/eShopOnContainers/src/Services/Catalog/Catalog.API/Infrastructure/CatalogContext.cs

• Basket: SourceCode/eShopOnContainers/src/Services/Basket/Basket.API/Controllers/BasketController.cs, SourceCode/eShopOnContainers/src/Services/Basket/Basket.API/Repositories/RedisBasketRepository.cs

• Ordering API/domain/infrastructure: SourceCode/eShopOnContainers/src/Services/Ordering/Ordering.API/Application/Commands/CreateOrderCommandHandler.cs, SourceCode/eShopOnContainers/src/Services/Ordering/Ordering.Domain/AggregatesModel/OrderAggregate/Order.cs, SourceCode/eShopOnContainers/src/Services/Ordering/Ordering.Infrastructure/OrderingContext.cs.

Identity, payment, notifications, and webhooks

Identity is a dedicated authentication/authorization server with its own EF user store and interactive account/consent UI. Payment reacts to order stock-confirmation events and publishes payment outcome events. Ordering status changes fan out to a SignalR hub and optional webhook subscriptions.

• Identity: SourceCode/eShopOnContainers/src/Services/Identity/Identity.API/Program.cs, SourceCode/eShopOnContainers/src/Services/Identity/Identity.API/Data/ApplicationDbContext.cs

• Payment: SourceCode/eShopOnContainers/src/Services/Payment/Payment.API/IntegrationEvents/EventHandling/OrderStatusChangedToStockConfirmedIntegrationEventHandler.cs

• Realtime updates: SourceCode/eShopOnContainers/src/Services/Ordering/Ordering.SignalrHub/NotificationHub.cs

• Webhook delivery/subscriptions: SourceCode/eShopOnContainers/src/Services/Webhooks/Webhooks.API/Controllers/WebhooksController.cs, SourceCode/eShopOnContainers/src/Services/Webhooks/Webhooks.API/Services/WebhooksSender.cs.

Event-driven checkout flow

Checkout crosses service boundaries asynchronously: Basket publishes UserCheckoutAccepted; Ordering creates and advances an order; Catalog confirms or rejects stock; Payment reports success/failure; Ordering publishes status events for clients and webhooks. Shared EventBus abstractions isolate business services from transport choice, while EF integration-event logs and resilient transactions support persistence-to-publication reliability.

• Event contracts/handlers: SourceCode/eShopOnContainers/src/Services/Basket/Basket.API/IntegrationEvents/Events/UserCheckoutAcceptedIntegrationEvent.cs, SourceCode/eShopOnContainers/src/Services/Ordering/Ordering.API/Application/IntegrationEvents/EventHandling/UserCheckoutAcceptedIntegrationEventHandler.cs

• Transport implementations: SourceCode/eShopOnContainers/src/BuildingBlocks/EventBus/EventBusRabbitMQ/EventBusRabbitMQ.cs, SourceCode/eShopOnContainers/src/BuildingBlocks/EventBus/EventBusServiceBus/EventBusServiceBus.cs

• Outbox-style event log: SourceCode/eShopOnContainers/src/BuildingBlocks/EventBus/IntegrationEventLogEF/Services/IntegrationEventLogService.cs.

Runtime, data, and deployment boundaries

The primary runtime is .NET/ASP.NET Core in Docker containers; the SPA additionally uses Angular/Node tooling. Services expose HTTP APIs and selected gRPC contracts. SQL-backed EF contexts serve catalog, ordering, identity, and webhooks; Redis serves baskets. RabbitMQ is provisioned for local/Kubernetes messaging, while Azure templates support SQL, Redis, Service Bus, Cosmos DB, and storage. ELK deployment assets provide centralized logging.

• Composition: SourceCode/eShopOnContainers/src/docker-compose.yml, SourceCode/eShopOnContainers/src/docker-compose.elk.yml

• Kubernetes service charts: SourceCode/eShopOnContainers/deploy/k8s/helm/ordering-api/Chart.yaml, SourceCode/eShopOnContainers/deploy/k8s/helm/rabbitmq/Chart.yaml

• Azure infrastructure: SourceCode/eShopOnContainers/deploy/azure/az/servicebus/sbusdeploy.json, SourceCode/eShopOnContainers/deploy/azure/az/sql/sqldeploy.json.