Deployment Diagram

Maps containers onto infrastructure. Where a container diagram cannot answer "where does this run?".

• Format.puml
• Length23 lines
• LibraryC4-PlantUML

The source

23 lines of PlantUML, and pulls in C4-PlantUML. Copy it, or open the template inside Gnomon and render it as it is.

@startuml
!include https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/master/C4_Deployment.puml

title Deployment Diagram

Deployment_Node(cloud, "Cloud Provider", "AWS") {
  Deployment_Node(vpc, "VPC") {
    Deployment_Node(web_tier, "Web Tier") {
      Container(web, "Web App", "Nginx + Vue.js")
    }
    Deployment_Node(app_tier, "Application Tier") {
      Container(api, "API", "Node.js")
    }
    Deployment_Node(data_tier, "Data Tier") {
      ContainerDb(db, "Database", "RDS PostgreSQL")
    }
  }
}

Rel(web, api, "HTTPS")
Rel(api, db, "SQL")

@enduml

Others in C4 model diagrams

• Context DiagramThe one to draw first, and often the only one a stakeholder needs.
• Container DiagramIndependently deployable or runnable things: a service, a database, a SPA. Not classes.
• Component DiagramInside one container. Draw this only when a container is big enough to need it.
• Dynamic DiagramFor a specific flow through the static structure: numbered steps, one scenario.