Architecturearchitecturecloudinfrastructure
Cloud Architecture Diagram
Start a Mermaid architecture diagram with web, API, worker, database, storage, and queue services grouped by cloud boundary.
Use Cases
Show infrastructure components in a cloud design review
Explain worker and queue relationships
Create a compact deployment diagram for documentation
Align engineering and operations on which runtime components live inside the cloud boundary
How This Workflow Works
| Step | Purpose |
|---|---|
| Cloud boundary | Groups the services that run inside the selected cloud platform or deployment environment. |
| Web app | Represents the user-facing runtime that sends application requests into backend services. |
| API service | Coordinates database access and asynchronous work after receiving requests from the web app. |
| Queue and worker | Shows background processing that decouples long-running work from user-facing requests. |
| Database and storage | Separates structured data storage from object storage used for files, exports, or assets. |
How To Customize
Rename the group and services to your cloud provider naming
Add caches, search indexes, or observability services
Update arrows to show the dominant runtime dependencies
Split web, API, and worker services by region or environment when needed
Add managed services such as secrets, CDN, pub/sub, or object lifecycle policies
Edit This Template Visually
Open this template in the editor to work from the rendered diagram and the Mermaid source together. Click a node in supported flowchart and sequence diagrams to locate the matching code, select source lines to find the related shape, or ask AI to rename, expand, restyle, or rewrite the selected part of the workflow.
Mermaid Source
architecture-beta
group cloud(cloud)[Cloud Platform]
service web(server)[Web App] in cloud
service api(server)[API Service] in cloud
service worker(server)[Worker] in cloud
service queue(queue)[Queue] in cloud
service db(database)[Database] in cloud
service storage(disk)[Object Storage] in cloud
web:R --> L:api
api:R --> L:db
api:B --> T:queue
queue:R --> L:worker
worker:R --> L:storage