How iam-veeramalla/three-tier-architecture-demo works
Main Components
• Frontend Component: The “web” service (using Docker for Nginx + static files) serves as the externally facing storefront.
• Business Logic / Microservices: Several independent microservices exist – for example, cart, catalogue, dispatch, payment, ratings, shipping, and user. Each service is built with different technology stacks (NodeJS for cart and user, Java for shipping, Go for dispatch, PHP for ratings, etc.). Also note that there is a load generator (load-gen) which simulates user behavior.
• Data Stores: There are containerized databases and caches such as MongoDB, MySQL, Redis, and message brokers like RabbitMQ.
• Infrastructure / Monitoring: Side components include configuration for container orchestration (Kubernetes helm charts, Docker Compose files, etc.) plus integrations with Instana for full end-to-end tracing and Prometheus metrics endpoints exposed by some services.
Relationships and Interactions
• External users make requests to the web storefront. The web service is the entry-point where requests enter the system.
• The web service interfaces with backend microservices (e.g., cart, catalogue, payment, shipping, user) to process business logic.
• Services interact with each other as needed – for example, the cart service might communicate with catalogue to retrieve product info, and the payment service receives data from the cart.
• Data transactions occur with databases (e.g., MongoDB for non-relational data, MySQL for relational data, Redis for caching) and messaging via RabbitMQ for decoupling.
• The load generator and monitoring components (i.e., Instana instrumentation) help capture performance data and simulate loads.
Architectural Patterns and Deployment Strategies
• Microservices Architecture: Each service is independently containerized and deployed either via Docker Compose or orchestrated on platforms like Kubernetes, DCOS, or Swarm.
• Use of Helm Charts and Cloud-Specific Directories: The presence of dedicated directories for AKS, EKS, GKE, K8s, OpenShift, etc. indicates that while the service design remains consistent, the deployment tooling and configurations vary. Represent these as deployment environments or orchestration platforms that encapsulate the microservices.
Technologies and Integration Points
• For services, note the languages and frameworks (e.g., NodeJS for cart and user, Java/Spring Boot for shipping, etc.).
• Databases (MongoDB, MySQL, Redis) and external integrations such as RabbitMQ.
• That services expose Prometheus metrics endpoints (notably cart and payment) to facilitate monitoring.
• Optionally, note Instana’s role for distributed tracing and monitoring (this might be shown as an overlay monitoring service that “watches” all microservice interactions).