How dchinthan/global-multi-tenant-saas-platform works
This repository is a cloud-native, multi-tenant SaaS reference platform: Terraform provisions its AWS service architecture, with a Helm/Kubernetes path for the fileservice. The documented principal flow routes a user through DNS, CDN and load balancing to ECS services; asynchronous work proceeds through EventBridge, SQS and Lambda toward data stores. Distinct capabilities include tenant identity, analytics/reporting, security, observability, disaster recovery, and EKS/AKS portability. Connections are based on README statements and diagrams; unsampled Terraform wiring is represented at module-directory level, not inferred in detail.
Main entry points: compute ECS Fargate · app5-fileservice Fileservice chart · edge Route 53 · main.py Fileservice
Components 20
Traffic entry
- Route 53
infra/terraform/modules/edge - CloudFront
infra/terraform/modules/edge - HTTP load balancer
infra/terraform/modules/compute
SaaS services
- Primary service
services/app1-python/app.py - Fileservice
services/app5-fileservice/main.py - Tenant identity
infra/terraform/modules/identity - Analytics
infra/terraform/modules/analytics - Scheduled reporting
services/reporting/scheduled_report_lambda.py
Cloud platform
- ECS Fargate
infra/terraform/modules/compute - EventBridge
infra/terraform/modules/event_backbone - SQS
infra/terraform/modules/event_backbone - Async Lambda
infra/terraform/modules/compute/lambda.tf - Tenant data stores
infra/terraform/modules/data
Platform operations
- Security controls
infra/terraform/modules/security - Logs and tracing
infra/terraform/modules/observability - Disaster recovery
infra/terraform/modules/disaster_recovery
Kubernetes path
- AWS Kubernetes
infra/terraform/modules/eks - Azure Kubernetes
infra/terraform/modules/azure_aks - Fileservice chart
helm/app5-fileservice
Other components
- SaaS user
Connections 13
- SaaS user → Route 53: requests
README.md - Route 53 → CloudFront: routes to
README.md - CloudFront → HTTP load balancer: forwards to
README.md - HTTP load balancer → ECS Fargate: routes HTTP
README.md - ECS Fargate → Primary service: hosts service
README.md - ECS Fargate → Fileservice: hosts service
README.md - EventBridge → SQS: dispatches events
README.md - SQS → Async Lambda: triggers async work
README.md - Async Lambda → Tenant data stores: uses stores
README.md - Analytics → Scheduled reporting: supports reporting
README.md - Fileservice → Fileservice chart: deployed with
README.md - Fileservice chart → AWS Kubernetes: deploys on
README.md - Fileservice chart → Azure Kubernetes: deploys on
README.md