How mag1305/ecommerce-microservice-backend-app works
Project type and purpose
• This is a cloud-native, Spring Boot–based microservices backend for an e-commerce system.
• It implements 10 µServices (user, product, favourite, order, shipping, payment) plus supporting services (service-discovery, cloud-config, api-gateway, proxy-client) and uses Docker, Kubernetes, Eureka, Config Server, Zipkin, Prometheus, MySQL/H2, Kafka.
File structure
• Top-level modules:
– service-discovery (Eureka registry)
– cloud-config (centralized configuration)
– api-gateway (Spring Cloud Gateway or Zuul)
– proxy-client (authentication/authorization proxy)
– user-service, product-service, favourite-service, order-service, shipping-service, payment-service (domain µServices)
• Shared POM and wrapper files for Maven across modules.
• k8s folder contains Kubernetes manifests for each service.
README for additional insights
• Confirms Spring Cloud design patterns: discovery, config, gateway, circuit breakers, reactive programming, TDD, logging/monitoring (Zipkin, Prometheus).
• Describes runtime landscape: Docker Compose (Kafka, Zipkin, DB) and planned Kubernetes deployment.
Elements
– Clear, concise labels for every component (e.g., “user-service”, “api-gateway”)
• Edge/Ingress (proxy-client, api-gateway)
• Control Plane (service-discovery, cloud-config)
• Domain µServices (user, product, order, etc.)
• Infrastructure (K8s cluster boundary)
Detailed capture of essential elements
• Inside it, group the µServices and infrastructure services in separate sub-zones.
• External clients outside the boundary at the top or left.
• Optionally number the interaction steps to reflect request sequence.