How kashifjaved1/ecommercestoremicroservices works
Project type and purpose
• This is a full-stack microservices e-commerce application.
• Purpose: provide shopping-cart, catalog, discount, and ordering functionality behind an API gateway, plus a Razor Pages web UI.
File structure
• Top-level modules under src:
• ApiGateways
– OcelotApiGateway: single entrypoint for all clients
– Shopping.Aggregator: composite façade that calls downstream services and exposes a unified shopping API
• BuildingBlocks/EventBus.Messages: shared contracts for integration events
• Services: each folder implements a microservice
– Basket.API (handles cart operations, publishes BasketCheckoutEvent)
– Catalog.API (CRUD on product catalog)
– Discount.API + Discount.Grpc (REST + gRPC endpoints for coupon service)
– Ordering.API + Application + Domain + Infrastructure (order management, consumes BasketCheckoutEvent)
• WebApps/eCommerceUI: ASP.NET Razor Pages UI that calls the gateway
• Docker-related: Dockerfiles in each service, docker-compose.yml for local orchestration
• Solution and launchSettings coordinate local development
README
• Minimal content; relies on code structure for architectural insight.
• Containers and their boundaries.
• Technology stack on each.
• Inter-service events and external dependencies.