{"id":15056,"date":"2026-01-14T13:35:17","date_gmt":"2026-01-14T05:35:17","guid":{"rendered":"https:\/\/www.cybermedian.com\/in\/docs\/my-document\/chapter-1\/hierarchy-overview\/"},"modified":"2026-01-15T11:06:35","modified_gmt":"2026-01-15T03:06:35","slug":"hierarchy-overview","status":"publish","type":"docs","link":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/","title":{"rendered":"Hierarchy Overview"},"content":{"rendered":"

Introduction to the four core levels (Context, Container, Component, Code) and three supporting views (Landscape, Dynamic, Deployment)<\/strong><\/p>\n

The true power of the C4 Model<\/strong> lies in its elegant, zoomable hierarchy. Rather than forcing everything into a single overwhelming diagram, the model organizes architecture visualization into distinct levels of abstraction. You start at the highest, broadest view and progressively “zoom in” to reveal more detail \u2014 exactly as needed for the audience and purpose.<\/p>\n

This hierarchy ensures clarity, focus, and scalability: each diagram has one clear responsibility, and you never show more (or less) than is useful at that moment.<\/p>\n

The Four Core Levels (the “C4”)<\/h3>\n
    \n
  1. Level 1: System Context Diagram<\/strong>\n
      \n
    • What it shows<\/strong>: Your entire software system as one single box<\/strong>, surrounded by its users (Persons<\/strong>) and any external systems it interacts with.<\/li>\n
    • Key elements<\/strong>: People (users, actors), external software systems, and high-level relationships.<\/li>\n
    • Level of detail<\/strong>: Very high \u2014 no technologies, no internal structure.<\/li>\n
    • Primary audience<\/strong>: Non-technical stakeholders, executives, product managers, new team members, auditors.<\/li>\n
    • Typical questions answered<\/strong>: What is the system? Who uses it? What does it connect to externally? Why does it exist?<\/li>\n
    • When to use<\/strong>: Almost always \u2014 this is the starting point for any architecture discussion or onboarding.<\/li>\n<\/ul>\n<\/li>\n
    • Level 2: Container Diagram<\/strong>\n
        \n
      • What it shows<\/strong>: Zooms inside the software system to reveal the major runnable or deployable units<\/strong> \u2014 web applications, mobile apps, APIs\/backends, databases, message brokers, file systems, microservices, serverless functions, etc.<\/li>\n
      • Key elements<\/strong>: Containers, the technologies chosen for each, and how containers communicate (protocols, APIs, queues, etc.).<\/li>\n
      • Level of detail<\/strong>: Medium \u2014 shows high-level technical building blocks and their interactions, but not internal implementation.<\/li>\n
      • Primary audience<\/strong>: Developers, architects, DevOps\/operations teams, technical stakeholders.<\/li>\n
      • Typical questions answered<\/strong>: What are the major deployable parts? Which technologies are used? How do they talk to each other?<\/li>\n
      • When to use<\/strong>: Whenever you need to understand or communicate the high-level technical architecture.<\/li>\n<\/ul>\n<\/li>\n
      • Level 3: Component Diagram<\/strong>\n
          \n
        • What it shows<\/strong>: Zooms into one specific container<\/strong> to reveal its internal logical building blocks \u2014 modules, services, libraries, subsystems, bounded contexts, web controllers, business logic layers, data access components, etc.<\/li>\n
        • Key elements<\/strong>: Components, their responsibilities, and the interfaces\/relationships between them.<\/li>\n
        • Level of detail<\/strong>: Detailed but still conceptual \u2014 focuses on logical structure and design decisions, not code-level classes or methods.<\/li>\n
        • Primary audience<\/strong>: Developers working inside that container, architects reviewing modularity or refactoring plans.<\/li>\n
        • Typical questions answered<\/strong>: How is this container internally structured? What are the key modules\/services? Where are the boundaries and interfaces?<\/li>\n
        • When to use<\/strong>: Selectively \u2014 only when the internal structure of a container adds meaningful value (e.g., complex domains, legacy monoliths being decomposed, critical services).<\/li>\n<\/ul>\n<\/li>\n
        • Level 4: Code Diagram<\/strong>\n
            \n
          • What it shows<\/strong>: The most granular view \u2014 implementation details inside a single component (or small set of components).<\/li>\n
          • Key elements<\/strong>: Classes, interfaces, enums, data structures, relationships (inheritance, composition, dependencies), or even database schemas (ERDs).<\/li>\n
          • Level of detail<\/strong>: Very detailed \u2014 often uses UML class diagrams, sequence diagrams, or auto-generated code structure views.<\/li>\n
          • Primary audience<\/strong>: Developers implementing or maintaining specific code.<\/li>\n
          • Typical questions answered<\/strong>: How is this component actually implemented in code? What classes handle what?<\/li>\n
          • When to use<\/strong>: Rarely and judiciously \u2014 only when code-level clarity is genuinely required (e.g., onboarding to a tricky area, security audits of critical code paths). Most teams stop at Level 3.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n

            The Three Supporting Views<\/h3>\n

            These are not part of the core “zoom” hierarchy but provide essential complementary perspectives:<\/p>\n

              \n
            • System Landscape Diagram<\/strong> A high-level, enterprise-wide view showing multiple software systems<\/strong> and their relationships across the organization. Think of it as a “zoomed-out” System Context diagram that includes many internal systems, not just one. Used for: portfolio visibility, enterprise architecture overviews, identifying integration points.<\/li>\n
            • Dynamic Diagram<\/strong> Focuses on runtime behavior<\/strong> rather than static structure. Shows how elements (persons, containers, or components) interact for a specific use case, scenario, or workflow \u2014 similar to a simplified UML sequence or collaboration diagram. Used for: explaining key flows, message exchanges, event-driven behavior, onboarding to business processes.<\/li>\n
            • Deployment Diagram<\/strong> Maps containers<\/strong> (Level 2) to physical or virtual infrastructure \u2014 servers, cloud regions, Kubernetes clusters, load balancers, networks, availability zones, etc. Shows runtime topology, scaling, redundancy, and infrastructure choices. Used for: DevOps\/operations discussions, capacity planning, security reviews, disaster recovery planning.<\/li>\n<\/ul>\n

              Together, these seven diagram types (4 core levels + 3 supporting views) form a complete yet lightweight toolkit. You choose only the views you need \u2014 there is no obligation to create all of them.<\/p>\n

              This flexible, hierarchical structure is what makes the C4 Model so powerful: it adapts to the size of your system, the maturity of your team, and the needs of your stakeholders, while keeping every diagram focused, understandable, and maintainable.<\/p>\n","protected":false},"featured_media":0,"parent":15038,"menu_order":3,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-15056","docs","type-docs","status-publish","hentry"],"yoast_head":"\nHierarchy Overview - 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-1-foundations-of-the-c4-model\/hierarchy-overview\/\" \/>\n<meta property=\"og:locale\" content=\"hi_IN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Hierarchy Overview - Cybermedian Indian\" \/>\n<meta property=\"og:description\" content=\"Introduction to the four core levels (Context, Container, Component, Code) and three supporting views (Landscape, Dynamic, Deployment) The true power\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/\" \/>\n<meta property=\"og:site_name\" content=\"Cybermedian Indian\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-15T03:06:35+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-1-foundations-of-the-c4-model\/hierarchy-overview\/\",\"url\":\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/\",\"name\":\"Hierarchy Overview - Cybermedian Indian\",\"isPartOf\":{\"@id\":\"https:\/\/www.cybermedian.com\/in\/#website\"},\"datePublished\":\"2026-01-14T05:35:17+00:00\",\"dateModified\":\"2026-01-15T03:06:35+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/#breadcrumb\"},\"inLanguage\":\"hi-IN\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/#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 1: Foundations of the C4 Model\",\"item\":\"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Hierarchy Overview\"}]},{\"@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":"Hierarchy Overview - 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-1-foundations-of-the-c4-model\/hierarchy-overview\/","og_locale":"hi_IN","og_type":"article","og_title":"Hierarchy Overview - Cybermedian Indian","og_description":"Introduction to the four core levels (Context, Container, Component, Code) and three supporting views (Landscape, Dynamic, Deployment) The true power","og_url":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/","og_site_name":"Cybermedian Indian","article_modified_time":"2026-01-15T03:06:35+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-1-foundations-of-the-c4-model\/hierarchy-overview\/","url":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/","name":"Hierarchy Overview - Cybermedian Indian","isPartOf":{"@id":"https:\/\/www.cybermedian.com\/in\/#website"},"datePublished":"2026-01-14T05:35:17+00:00","dateModified":"2026-01-15T03:06:35+00:00","breadcrumb":{"@id":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/#breadcrumb"},"inLanguage":"hi-IN","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/hierarchy-overview\/#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 1: Foundations of the C4 Model","item":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/"},{"@type":"ListItem","position":4,"name":"Hierarchy Overview"}]},{"@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\/15056","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=15056"}],"version-history":[{"count":2,"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs\/15056\/revisions"}],"predecessor-version":[{"id":15060,"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs\/15056\/revisions\/15060"}],"up":[{"embeddable":true,"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs\/15038"}],"prev":[{"title":"The Problem of Traditional Diagramming","link":"https:\/\/www.cybermedian.com\/in\/docs\/mastering-c4-model\/module-1-foundations-of-the-c4-model\/the-problem-of-traditional-diagramming\/","href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/docs\/15050"}],"wp:attachment":[{"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/media?parent=15056"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.cybermedian.com\/in\/wp-json\/wp\/v2\/doc_tag?post=15056"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}