How swayam-prakash-bhuyan/sock-shop-demo works
Project type and purpose
• This is the “Sock Shop” reference microservices demo: a full-stack, containerized, multi-architecture e-commerce application built to showcase cloud-native and microservice patterns on Kubernetes/OpenShift.
• It comprises eight independent microservices (front-end, carts, catalogue, orders, payment, user, shipping, queue-master) plus backing databases and a message broker (RabbitMQ).
File structure
• Top-level “automation” folder holds Dockerfiles for each microservice and its supporting DB container (e.g., Dockerfile-carts, Dockerfile-catalogue, Dockerfile-user-db, etc.).
• “manifests” contains a Kustomize base (manifests/base) defining Deployments, Services, PVCs for each component, plus overlays (manifests/overlays/…) for different deployment scenarios (fyre, multi, multi-hpa, power, etc.).
README for architecture insights
• Lists each microservice and its repo, and notes the use of Spring Boot, Go kit, Node.js.
• Describes three deployment overlays (fyre, multi, multi-hpa) showing that k8s is a primary platform.
• Links to an existing “Architecture.png” showing service interactions and data flow between UI, services, queues, and databases.
a. Main components
• External: Browser or API client.
• Front-end service (Node.js).
• Backend microservices: carts, catalogue, orders, payment, user, shipping, queue-master.
• Message broker: RabbitMQ.
• Databases: carts-db, catalogue-db, orders-db, user-db, session-db.
• Kubernetes constructs: Deployments (Pods), Services, PVCs; Route/Ingress for front-end.
b. Relationships & interactions
• Browser → front-end (HTTP/HTTPS).
• front-end → API calls to carts, catalogue, orders, payment, user, shipping (HTTP/gRPC).
• carts, orders, shipping, payment may publish/consume events via queue-master & RabbitMQ.
• Each service reads/writes its own database.
• session-db used by front-end or user service for session persistence.
c. Architectural patterns & principles
• Independent microservices, each with its own data store (database per service pattern).
• API gateway / UI layer (front-end) decouples client from microservices.
• Asynchronous messaging for certain flows (via RabbitMQ + queue-master).
• Containerization + Kubernetes native objects (Deployments, Services, PVCs, HPA in multi-hpa overlay).
• Multi-architecture image support for heterogeneous clusters.
d. Key technologies
• Node.js (front-end), Spring Boot (orders, payment, user, shipping), Go kit (catalogue, queue-master, carts).
• Docker, Kubernetes (Kustomize manifests, Deployments/Services), OpenShift Route or Ingress.
• RabbitMQ for messaging, MongoDB or equivalent for microservice databases.