$ show Azure-Samples/aks-store-demo
The AKS Store Demo is a polyglot microservices application designed to demonstrate deployment patterns on Azure Kubernetes Service (AKS). It simulates an online pet store where users can browse products, place orders, and administrators can manage inventory and view orders. The system comprises multiple independently deployable services: a Vue.js storefront and admin panel, a Node.js order service, a Go makeline service for order processing, a Rust product service for catalog management, a Python AI service for optional generative AI features, and Rust-based virtual customer and worker services for traffic simulation. Services communicate via REST APIs and a message queue (RabbitMQ or Azure Service Bus), with data persisted in DocumentDB (Azure Cosmos DB with MongoDB API). The application showcases strong engineering practices through its use of infrastructure-as-code (Terraform and Bicep), Kubernetes manifests managed via Kustomize for environment-specific configuration, and Azure Developer CLI (azd) hooks for automated provisioning and deployment. Each service includes health checks, Docker multi-stage builds, and observability hooks. The polyglot nature allows each service to use the most suitable language for its function, while the clear separation of concerns and well-defined interfaces enable independent development and scaling. The repository includes comprehensive unit, end-to-end, and traffic simulation tests to ensure reliability.
The LLM identified 2 files worth highlighting for reuse:
The kustomize directory provides a base set of Kubernetes manifests for all services, with overlays for different environments (e.g., azd, dev, kaito). This pattern allows for environment-specific customization (like resource names, replica counts, or image tags) without duplicating base manifests, promoting DRY principles and reducing configuration drift. It is easily extractable to other Kubernetes projects.
The azd-hooks directory contains PowerShell and shell scripts that run before and after deployment and provisioning steps when using the Azure Developer CLI. These hooks automate tasks such as setting up environment variables, configuring custom values for Helm charts, and post-deployment validation. This pattern encapsulates Azure-specific deployment logic in a reusable and isolated manner, reducing manual steps and ensuring consistency across deployments.