{"id":15089,"date":"2026-01-14T13:53:53","date_gmt":"2026-01-14T05:53:53","guid":{"rendered":"https:\/\/www.cybermedian.com\/in\/docs\/my-document\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/"},"modified":"2026-01-15T13:36:37","modified_gmt":"2026-01-15T05:36:37","slug":"deployment-mapping","status":"publish","type":"docs","link":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/","title":{"rendered":"Deployment Mapping"},"content":{"rendered":"<p dir=\"auto\"><strong>Visualizing how containers map to physical or virtual infrastructure (Level 2\/Deployment synergy)<\/strong><\/p>\n<p dir=\"auto\">The <strong>Deployment Diagram<\/strong> (one of the three supporting views in the C4 Model) bridges the logical architecture defined in Level 2 (Container Diagram) with the real-world runtime environment. It shows <strong>how<\/strong> the containers are actually deployed, hosted, scaled, and connected in production \u2014 mapping the abstract, technology-focused containers to concrete infrastructure elements such as servers, cloud services, clusters, networks, and availability zones.<\/p>\n<p dir=\"auto\">This view is essential because logical architecture (what containers exist and how they communicate) does <strong>not<\/strong> always match physical reality. A single container might run as multiple replicas, a database might be clustered across regions, or several containers might share the same Kubernetes namespace. The Deployment Diagram makes these decisions visible and explicit.<\/p>\n<h3 dir=\"auto\">Purpose of the Deployment Diagram<\/h3>\n<p dir=\"auto\">It answers critical operational and infrastructure-related questions:<\/p>\n<ul dir=\"auto\">\n<li>Where (physically or virtually) do each container\u2019s instances run?<\/li>\n<li>How is scaling, high availability, and fault tolerance achieved?<\/li>\n<li>What infrastructure components (load balancers, gateways, firewalls, CDNs) sit between containers or between containers and users?<\/li>\n<li>How are environments separated (dev, staging, production)?<\/li>\n<li>What are the network boundaries, security groups, or trust zones?<\/li>\n<li>How does the deployment topology affect latency, resilience, cost, or compliance?<\/li>\n<\/ul>\n<p dir=\"auto\">This diagram is the natural companion to the Container Diagram \u2014 they are often created together or iteratively refined as infrastructure evolves.<\/p>\n<h3 dir=\"auto\">Key Elements of a Deployment Diagram<\/h3>\n<ol dir=\"auto\">\n<li><strong>Deployment Nodes<\/strong>\n<ul dir=\"auto\">\n<li>Represent physical or virtual infrastructure hosts.<\/li>\n<li>Common types:\n<ul dir=\"auto\">\n<li>Physical servers (\u201cOn-prem Server\u201d)<\/li>\n<li>Virtual machines (\u201cEC2 Instance m5.large\u201d)<\/li>\n<li>Kubernetes clusters (\u201cEKS Cluster \u2013 us-east-1\u201d)<\/li>\n<li>Cloud regions or availability zones (\u201cAWS us-west-2a\u201d)<\/li>\n<li>Serverless execution environments (\u201cAWS Lambda\u201d)<\/li>\n<li>PaaS platforms (\u201cHeroku Dyno\u201d, \u201cAzure App Service\u201d)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><strong>Containers<\/strong> (from Level 2)\n<ul dir=\"auto\">\n<li>Placed <strong>inside<\/strong> deployment nodes to show where they run.<\/li>\n<li>Show <strong>instances\/replicas<\/strong> when relevant:\n<ul dir=\"auto\">\n<li>\u201cOrder Service (3 replicas)\u201d<\/li>\n<li>\u201cPostgreSQL \u2013 Primary + 2 Replicas\u201d<\/li>\n<\/ul>\n<\/li>\n<li>Multiple containers can run on the same node (e.g., in a monolith or shared VM).<\/li>\n<li>A single container type can appear in multiple nodes (e.g., scaled horizontally).<\/li>\n<\/ul>\n<\/li>\n<li><strong>Infrastructure Supporting Elements<\/strong>\n<ul dir=\"auto\">\n<li>Load balancers (\u201cALB \u2013 Application Load Balancer\u201d)<\/li>\n<li>API gateways \/ ingress controllers (\u201cKong Ingress\u201d, \u201cNGINX Ingress\u201d)<\/li>\n<li>Message brokers when deployed separately (\u201cKafka Cluster \u2013 3 brokers\u201d)<\/li>\n<li>Databases with clustering (\u201cAurora PostgreSQL \u2013 Multi-AZ\u201d)<\/li>\n<li>CDNs, firewalls, VPNs, service meshes (\u201cIstio\u201d, \u201cAWS WAF\u201d)<\/li>\n<li>External services treated as nodes (\u201cStripe \u2013 Payment Service \u2013 External\u201d)<\/li>\n<\/ul>\n<\/li>\n<li><strong>Relationships &amp; Communication Paths<\/strong>\n<ul dir=\"auto\">\n<li>Show <strong>runtime connections<\/strong> between nodes or between containers across nodes.<\/li>\n<li>Label with protocols when different from Level 2 (e.g., \u201cInternal VPC traffic\u201d, \u201cHTTPS over public internet\u201d, \u201cPrivateLink\u201d).<\/li>\n<li>Indicate redundancy or failover paths (e.g., dashed lines for standby replicas).<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<h3 dir=\"auto\">Level 2 \/ Deployment Synergy \u2014 How They Work Together<\/h3>\n<p dir=\"auto\">The Container Diagram (Level 2) and Deployment Diagram are tightly coupled:<\/p>\n<ul dir=\"auto\">\n<li><strong>Container Diagram<\/strong> answers: \u201cWhat are the major deployable units, their technologies, and how do they logically interact?\u201d \u2192 Focus: responsibility, protocol, abstraction<\/li>\n<li><strong>Deployment Diagram<\/strong> answers: \u201cHow are those units physically\/virtualized deployed, scaled, and networked in the real world?\u201d \u2192 Focus: instances, hosts, redundancy, infrastructure topology<\/li>\n<\/ul>\n<p dir=\"auto\">Example synergy:<\/p>\n<ul dir=\"auto\">\n<li>Container Diagram shows \u201cOrder Service (Spring Boot)\u201d \u2194 \u201cPostgreSQL \u2013 Orders\u201d via \u201cJDBC\u201d<\/li>\n<li>Deployment Diagram shows:\n<ul dir=\"auto\">\n<li>\u201cOrder Service\u201d running as 5 pods in \u201cEKS Cluster \u2013 prod-us-east-1\u201d<\/li>\n<li>\u201cPostgreSQL\u201d as Aurora cluster with primary in us-east-1a and replicas in us-east-1b\/c<\/li>\n<li>Traffic routed via \u201cALB\u201d \u2192 \u201cIngress Controller\u201d \u2192 pods<\/li>\n<li>Database access via \u201cRDS Proxy\u201d inside VPC<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\">This pairing reveals:<\/p>\n<ul dir=\"auto\">\n<li>Horizontal scaling realities<\/li>\n<li>Single points of failure (e.g., all pods in one AZ)<\/li>\n<li>Network hops and latency sources<\/li>\n<li>Security boundaries (public vs. private subnets)<\/li>\n<li>Cost drivers (number of instances, reserved capacity)<\/li>\n<\/ul>\n<h3 dir=\"auto\">When to Create a Deployment Diagram<\/h3>\n<ul dir=\"auto\">\n<li>You are operating in cloud-native, containerized, or hybrid environments (Kubernetes, ECS, serverless, VMs).<\/li>\n<li>Infrastructure decisions impact architecture (multi-region, high availability, cost optimization).<\/li>\n<li>Conducting security reviews, compliance audits, disaster recovery planning, or capacity analysis.<\/li>\n<li>Onboarding DevOps\/SRE teams or explaining production topology to developers.<\/li>\n<li>Migrating between environments (on-prem \u2192 cloud, monolithic \u2192 Kubernetes).<\/li>\n<\/ul>\n<p dir=\"auto\">Skip or keep very simple if:<\/p>\n<ul dir=\"auto\">\n<li>Everything runs on a single traditional server<\/li>\n<li>The system is purely serverless with no custom topology<\/li>\n<li>Infrastructure is trivial or fully managed<\/li>\n<\/ul>\n<h3 dir=\"auto\">Best Practices<\/h3>\n<ul dir=\"auto\">\n<li>Keep one diagram per major environment (e.g., \u201cProduction Deployment\u201d, \u201cStaging\u201d) or one high-level overview.<\/li>\n<li>Use icons or colors to distinguish node types (cloud provider logos, server vs. container symbols).<\/li>\n<li>Show redundancy explicitly (replicas, AZs, failover arrows).<\/li>\n<li>Avoid low-level details like exact IP addresses, pod names, or Helm values \u2014 stay at logical infrastructure level.<\/li>\n<li>Generate or maintain via tools (C4-PlantUML, Structurizr, IcePanel) for version control alongside code.<\/li>\n<\/ul>\n<p dir=\"auto\">The Deployment Diagram turns your logical architecture into an <strong>operational reality<\/strong> \u2014 making invisible infrastructure choices visible, actionable, and communicable. It completes the story: from business purpose (Level 1), through technical building blocks (Level 2), to how everything actually runs in the real world.<\/p>\n<p dir=\"auto\">In the hands-on section ahead, you\u2019ll take a Container Diagram from earlier modules, map its containers to realistic infrastructure (cloud or hybrid), add scaling\/redundancy, and draw the deployment topology that brings the architecture to life in production.<\/p>\n","protected":false},"featured_media":0,"parent":15086,"menu_order":2,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-15089","docs","type-docs","status-publish","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.7 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Deployment Mapping - Cybermedian Indian<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/\" \/>\n<meta property=\"og:locale\" content=\"hi_IN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Deployment Mapping - Cybermedian Indian\" \/>\n<meta property=\"og:description\" content=\"Visualizing how containers map to physical or virtual infrastructure (Level 2\/Deployment synergy) The Deployment Diagram (one of the three supporting\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/\" \/>\n<meta property=\"og:site_name\" content=\"Cybermedian Indian\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-15T05:36:37+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u0905\u0928\u0941\u092e\u093e\u0928\u093f\u0924 \u092a\u0922\u093c\u0928\u0947 \u0915\u093e \u0938\u092e\u092f\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 \u092e\u093f\u0928\u091f\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/\",\"url\":\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/\",\"name\":\"Deployment Mapping - Cybermedian Indian\",\"isPartOf\":{\"@id\":\"https:\/\/www.cybermedian.com\/in\/#website\"},\"datePublished\":\"2026-01-14T05:53:53+00:00\",\"dateModified\":\"2026-01-15T05:36:37+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/#breadcrumb\"},\"inLanguage\":\"hi-IN\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.cybermedian.com\/in\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering the C4 Model: From Foundations to AI-Powered Software Architecture Visualization\",\"item\":\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Module 5: Enterprise Visibility and Supporting Views\",\"item\":\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Deployment Mapping\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.cybermedian.com\/in\/#website\",\"url\":\"https:\/\/www.cybermedian.com\/in\/\",\"name\":\"Cybermedian Indian\",\"description\":\"Learning one new thing everyday\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.cybermedian.com\/in\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"hi-IN\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Deployment Mapping - Cybermedian Indian","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/","og_locale":"hi_IN","og_type":"article","og_title":"Deployment Mapping - Cybermedian Indian","og_description":"Visualizing how containers map to physical or virtual infrastructure (Level 2\/Deployment synergy) The Deployment Diagram (one of the three supporting","og_url":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/","og_site_name":"Cybermedian Indian","article_modified_time":"2026-01-15T05:36:37+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u0905\u0928\u0941\u092e\u093e\u0928\u093f\u0924 \u092a\u0922\u093c\u0928\u0947 \u0915\u093e \u0938\u092e\u092f":"4 \u092e\u093f\u0928\u091f"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/","url":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/","name":"Deployment Mapping - Cybermedian Indian","isPartOf":{"@id":"https:\/\/www.cybermedian.com\/in\/#website"},"datePublished":"2026-01-14T05:53:53+00:00","dateModified":"2026-01-15T05:36:37+00:00","breadcrumb":{"@id":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/#breadcrumb"},"inLanguage":"hi-IN","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/deployment-mapping\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cybermedian.com\/in\/"},{"@type":"ListItem","position":2,"name":"Mastering the C4 Model: From Foundations to AI-Powered Software Architecture Visualization","item":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/"},{"@type":"ListItem","position":3,"name":"Module 5: Enterprise Visibility and Supporting Views","item":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/"},{"@type":"ListItem","position":4,"name":"Deployment Mapping"}]},{"@type":"WebSite","@id":"https:\/\/www.cybermedian.com\/in\/#website","url":"https:\/\/www.cybermedian.com\/in\/","name":"Cybermedian Indian","description":"Learning one new thing everyday","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cybermedian.com\/in\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"hi-IN"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs\/15089","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/comments?post=15089"}],"version-history":[{"count":4,"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs\/15089\/revisions"}],"predecessor-version":[{"id":15180,"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs\/15089\/revisions\/15180"}],"up":[{"embeddable":true,"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs\/15086"}],"next":[{"title":"Level 4 \u2013 Code Diagrams","link":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/level-4-code-diagrams\/","href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs\/15090"}],"prev":[{"title":"Modeling Runtime Behavior","link":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-5-enterprise-visibility-and-supporting-views\/modeling-runtime-behavior\/","href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs\/15088"}],"wp:attachment":[{"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/media?parent=15089"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/doc_tag?post=15089"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}