Deployment Architecture
Create deployment architecture diagrams showing where components are deployed, including high availability, failover, and load balancing configurations.
Deployment architecture diagrams show where and how solution components are deployed. They document the runtime environment, infrastructure choices, and operational topology.
What Deployment Diagrams Show
A deployment architecture diagram typically includes:
Creating Deployment Diagrams
Platform-Specific Icons
Use the correct icon library for your platform:
| Platform | Icon Count | Coverage |
|---|---|---|
| Azure | 705 | Compute, networking, storage, databases |
| AWS | 309 | EC2, Lambda, RDS, S3, and more |
| Google Cloud | 19 | Core GCP service icons |
| Kubernetes | 39 | Pods, services, deployments, ingress |
| CNCF | 207 | Prometheus, Envoy, Istio, etc. |
High Availability Architecture
Document redundancy and failover configurations:
Load Balancer Configuration
Visualise traffic distribution:
Visual Conventions
| Element | Representation |
|---|---|
| Availability zones, regions, VPCs | Dashed rectangles |
| Physical or logical groupings | Solid rectangles |
| Redundant instances | Duplicate icons |
| Synchronisation or replication | Bidirectional arrows |
| Primary components | Blue colour |
| Secondary components | Grey colour |
| External components | Orange colour |
Best Practices
Show Real Topology
Document actual deployment, not idealised views.
Include Scale Indicators
Label instance counts or scaling ranges.
Document Regions
Geographic distribution matters for latency and compliance.
Show Dependencies
External services and managed services.
Version in Git
Deployment topology changes with releases.