What is microservices-demo?

This project is a fork of Google's Online Boutique demo application, an example online shop made up of about eleven small services, adapted here to show a full DevSecOps pipeline running on Amazon's EKS Kubernetes service. Rather than focusing on the shop's features, the point of this repository is to demonstrate how to build, secure, and deploy a microservices app on AWS from end to end. All of the cloud infrastructure, including the Kubernetes cluster, database, container registry, and load balancer, is defined as code using Terraform and applied automatically through a dependency ordered pipeline in GitHub Actions. Once the infrastructure exists, an ArgoCD controller continuously watches a folder of Kubernetes manifests in this repository and keeps the live cluster in sync with whatever is committed there, which is a pattern known as GitOps. The build pipeline that runs on every push does several things in sequence: it scans the code for accidentally committed secrets with Gitleaks, checks code quality with SonarQube's static analysis, builds Docker images only for the services that changed, scans those images for known vulnerabilities with Trivy, and finally pushes the images to a private container registry and commits the new image tags so ArgoCD picks them up. For monitoring, the cluster runs Prometheus and Grafana to collect and display metrics about both the infrastructure and the running application. DNS is handled automatically too: a tool called ExternalDNS watches for new load balancer addresses and creates the matching DNS records in Amazon Route 53, so nobody has to set up DNS records by hand. The repository is organized into a one-time bootstrap step for shared state storage, a terraform folder with separate modules for each piece of infrastructure, a kubernetes-manifests folder that ArgoCD watches, the source code for all the microservices, a teardown script for tearing down all AWS resources, and GitHub Actions workflow files for infrastructure, builds, and teardown. A companion article linked from the README walks through the full setup process step by step.