How aliouimohamedamine/devops-microservices works
Project type and purpose
• This is a full-stack, microservice-based e-commerce “Astronomy Shop” demo application, originally from the OpenTelemetry team, extended here with a complete DevOps pipeline.
• It includes 12+ back end microservices, a React web front end, a React-Native mobile front end, supporting infrastructure (Kafka, Envoy, feature‐flagging via FlagD), plus observability (OpenTelemetry, Prometheus, Grafana), all deployable locally (Docker Compose) or to AWS EKS using Terraform and ArgoCD.
File structure
• Top-level “src” directory holds directories for each microservice (accounting, ad, cart, checkout, currency, email, fraud-detection, image-provider, load-generator, payment, product-catalog, quote, recommendation, shipping, frontend, frontend-proxy, flagd-ui, flagd, react-native-app, kafka, otel-collector, prometheus, grafana).
• “eks” holds Terraform code for provisioning AWS VPC and EKS cluster modules.
• “kubernetes” holds YAML manifests for deploying each service into K8s.
• CI/CD config lives under “.github/workflows/ci.yaml” and likely ArgoCD Helm charts under “charts” (per README).
• “docker-compose.yml” for local multi-container startup.
README for additional insights
• Highlights: full CI/CD (GitHub Actions + ArgoCD), IaC (Terraform), containerization (Docker), orchestration (Kubernetes/EKS), monitoring (Prometheus + Grafana).
• Key use-cases: local dev via Docker Compose; Kubernetes cluster deployment; AWS Terraform apply.