How rahulsahay19/eshopping works
Project Type and Purpose
• This is a full-stack .NET Core microservices e-commerce application built with Clean Architecture.
• It comprises multiple independently deployable microservices (Basket, Catalog, Discount, Ordering), an Identity Server for authentication/authorization, an API Gateway (Ocelot + Nginx), a single-page Angular client, and a deployment/configuration layer using Docker, Kubernetes, Helm, Istio, and observability tools (ELK, Prometheus/Grafana).
File Structure
• Top-level directories:
• ApiGateways (Ocelot.ApiGateway + nginx)
• Infrastructure (shared logging, Identity Server)
• Services (Basket, Catalog, Discount, Ordering each following Clean Architecture: API, Application, Core, Infrastructure)
• client (Angular frontend)
• Deployments (helm charts, k8s yamls, Istio)
• PostmanCollection
• Each microservice follows the pattern:
– API layer (Controllers, Startup, Program, Dockerfile)
– Application layer (Commands/Queries, Handlers, DTOs, gRPC clients where needed)
– Core layer (Entities, Repositories interfaces, Specs)
– Infrastructure layer (EF Core or Mongo/Postgres context, repository implementations, migrations/seed data)
• Cross-cutting middleware and logging in Infrastructure/Common.Logging.
• Identity Server under Infrastructure/EShopping.Identity implements OAuth2/OIDC.
• docker-compose, Helm charts, and Istio manifests orchestrate multi-service deployment and mesh.
README Insights
• Confirms technologies: .NET Core, Docker, Kubernetes, IdentityServer4, RabbitMQ (pub/sub), gRPC (Discount), Redis (Basket), MongoDB (Catalog), PostgreSQL (Ordering), ELK Stack, Ocelot API Gateway, Nginx, Istio service mesh, Azure, Helm, Auto-scale.
• Shows high-level architecture, deployment topology, service mesh, CI/CD hints.
• Frontend (blue)
• Gateway/auth (purple)
• Microservices (green)
• Datastores (orange)
• Infra (gray)