Suggest an editImprove this articleRefine the answer for “What is an architecture diagram?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)An **architecture diagram** is a visual representation of a software system's structure: its components, the connections between them, and the principles of their interaction. It shows the overall design of the system, not the code. **Key point:** the goal of the diagram is to quickly explain the idea, not to impress.Shown above the full answer for quick recall.Answer (EN)ImageAn **architecture diagram** is a visual representation of a software system's structure: its components, the connections between them, and the principles of their interaction. It shows *not the code, but the overall design of the system* - who "talks" to whom, where data is stored, how requests flow, and where the bottlenecks might be. --- ### Why an architecture diagram is needed - helps **understand the system's logic** without diving into code details; - serves as a **common language** between developers, analysts, managers, and clients; - is used for **discussing, reviewing, and documenting** decisions; - allows you to **quickly assess risks and points of failure**. In simpler terms, it's a "map" of the product that lets you understand how it's built even if you're seeing it for the first time. --- ### Main types of architecture diagrams 1. **High-Level Architecture Diagram** Shows the system as a whole: external services, databases, APIs, frontend, backend, queues, clouds, and so on. Used for presentations and integration planning. Example: user → web application → API → database → analytics service. 2. **Component Diagram** Reveals which logical blocks make up the system: modules, services, libraries. Shows their dependencies and points of interaction. Example: "authorization module", "payments module", "notifications module". 3. **Deployment Diagram** Shows how the system is physically deployed - servers, containers, clusters, cloud services. It shows nodes, load balancers, databases, and their connections. Especially important for DevOps and when scaling. 4. **Sequence Diagram** Reflects *how requests flow* between components over time. For example: user makes a request → controller → service → database → response to the user. Used to analyze performance and business process logic. 5. **C4 model** A modern standard that splits architecture into 4 levels: - **Context** - who interacts with the system and how; - **Container** - what the system consists of (web application, database, API, and so on); - **Component** - the internal parts of containers; - **Code** - specific classes and methods. This model helps keep the same project understandable for people with different levels of involvement. --- ### What architecture diagrams are made with Popular tools: [**Draw.io**](http://Draw.io) **(**[**diagrams.net**](http://diagrams.net)**)**, **Lucidchart**, **Miro**, **PlantUML**, **Whimsical**, **Figma**. It's important that the diagram be clear, not "beautiful" - the goal is to quickly explain the idea, not to impress. --- ### Conclusion An architecture diagram is a visual way to show **how the system is built and how it lives**. It combines technical and business aspects in one picture, helping all project participants understand the product in the same way - *without extra words or guesswork*.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.