☁️ SaaS & Cloud · Deployment · Pro
Kubernetes Microservices Deployment
How a microservices app runs on Kubernetes in the cloud: ingress, namespaces, services with multiple replicas, managed databases and monitoring.
Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
What this diagram shows
- Ingress controller behind a cloud load balancer
- Each service runs as multiple pods with autoscaling
- Databases and cache are managed cloud services outside the cluster
Prompt used
Deployment diagram of microservices on a managed Kubernetes cluster (EKS) in AWS: users reach a load balancer and an NGINX ingress controller. The app namespace runs frontend, API, orders and payments deployments with 3 replicas each and horizontal pod autoscaling. Data lives in Amazon RDS PostgreSQL and ElastiCache Redis outside the cluster. A monitoring namespace runs Prometheus and Grafana.
Mermaid code
flowchart TB
U[Users] --> LB[AWS Load Balancer]
subgraph AWS[AWS Region ap-south-1]
subgraph EKS[EKS Cluster]
ING[NGINX Ingress]
subgraph NS[Namespace: app]
FE[frontend x3 pods]
API[api x3 pods]
ORD[orders x3 pods]
PAY[payments x2 pods]
end
subgraph MON[Namespace: monitoring]
PROM[Prometheus]
GRAF[Grafana]
end
end
RDS[(RDS PostgreSQL Multi-AZ)]
REDIS[(ElastiCache Redis)]
end
LB --> ING
ING --> FE
ING --> API
API --> ORD
API --> PAY
ORD --> RDS
PAY --> RDS
API --> REDIS
PROM -.scrapes.-> API
GRAF --> PROMRelated templates
CI/CD Pipeline Flowchart
A typical CI/CD pipeline from a pull request to production: build, tests, security scans, staging deploy, approval and a canary release.
OAuth 2.0 / OpenID Connect Login
The authorization code flow with PKCE used by most modern web and mobile apps to log users in through an identity provider.
Multi-Tenant SaaS Architecture
A B2B SaaS product serving many customer organisations from one platform: tenant-aware services, per-tenant data isolation, billing and admin.
AWS Three-Tier Web Application
The classic three-tier web app on AWS: CloudFront and a load balancer, an autoscaling app tier in private subnets, and a Multi-AZ database.
Event-Driven Architecture with Kafka
Services that talk through events instead of direct calls: an order service publishes events that inventory, payments, notifications and analytics react to.
SaaS Subscription Billing Lifecycle
The states of a SaaS customer's subscription: trial, active, past due with retries, paused, cancelled and expired.