Azure
Microservices
advanced
CQRS with Event Streaming — Azure Architecture Template
Command services on AKS write to SQL and publish to Event Hubs; projectors build Cosmos DB read models served by a read API.
Why this architecture works
- Separating write and read paths lets each side scale and be modeled for its own access pattern
- Event Hubs is the durable, replayable log — read models can be rebuilt from history at any time
- SQL guards transactional invariants on writes while Cosmos DB serves denormalized reads at low latency
- Projector functions are idempotent consumers, so redelivery never corrupts read models
- One API Management front door hides the CQRS split from clients entirely
What's inside (11 resources)
API Gateway
api-management
Images
container-registry
Write Services
kubernetes-service
Read API
function-app
Event Stream
event-hub-namespace
Projectors
function-app
Read Store
cosmos-db
Write Store
sql-database
SQL Server
sql-server
Secrets
key-vault
Logs
log-analytics-workspace
From template to running infrastructure
- Open this template in the CloudForge visual designer (free account, no credit card).
- Customize resources, names, and connections on the drag-and-drop canvas — or ask Vani, the AI architect, to adapt it.
- Generate production-ready Terraform, ARM, or Bicep in one click.
- Review the plan diff and security scan, then deploy with human approval.