Azure AKS microservices
Microservices on AKS behind Front Door + Application Gateway with hub-and-spoke networking, Cosmos DB, and Service Bus.
The prompt
Azure microservices architecture on AKS. Azure Front Door routes to a regional Application Gateway with WAF in East US. Application Gateway forwards to an AKS ingress controller. AKS runs three microservices: catalog, orders, payments. AKS uses Azure CNI in a dedicated spoke VNet. Workload identity provides pod-to-Azure auth. Cosmos DB for catalog, Azure SQL for orders, Service Bus for async messaging between services, Container Registry for images. Hub VNet contains Azure Firewall and VPN Gateway, peered to the spoke. Application Insights and Log Analytics for observability.
What it generates
A diagram of an enterprise-grade Azure microservices stack including hub-and-spoke networking, identity, data services, and observability.
When to use it
For enterprise Azure deployments where compliance and network segregation matter, and you need a hub-and-spoke topology rather than a flat VNet.
Generate this diagram in seconds
Copy the prompt above, sign in for free, and paste it into the generator.
Related cloud templates
AWS three-tier web application
Classic web app on AWS with CloudFront, ALB, ECS Fargate, and RDS Multi-AZ across two availability zones.
AWS serverless API
API Gateway + Lambda + DynamoDB with Cognito auth, async processing via SNS/SQS, and full observability.
Multi-region active-active deployment
Active-active app spanning two AWS regions with Route 53 latency-based routing, Aurora Global Database, and S3 cross-region replication.