> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/system-design/system-design-methodology/diagrams/uml-diagrams/plantuml/network-diagram.md).

# Network Diagram

## About

A Network Diagram represents the architecture and communication flow between different network components such as servers, clients, routers, firewalls, and databases. It is widely used for network infrastructure planning, cloud architecture, and distributed systems.

{% hint style="success" %}
Refer to the official documentation for more details - <https://plantuml.com/nwdiag>
{% endhint %}

### **Key Elements**

* **Nodes (Devices & Components)**
  * Represented as **rectangles or labeled icons**.
  * Examples: `Client`, `Web Server`, `Database`, `Load Balancer`.
* **Connections (Communication Links)**
  * Represented as **solid or dashed lines**.
  * Can indicate **protocols (e.g., HTTP, TCP/IP)**.
* **Firewalls & Security Layers**
  * Represented as a **shield or labeled box**.
  * Shows **network security boundaries**.
* **Cloud Services & External Systems**
  * Used to **represent external APIs, cloud storage, or third-party integrations**.
* **Clusters & Zones**
  * Represent **subnets, VLANs, data centers, or availability zones**.

## 1. Sample Network Diagram

```plant-uml
@startuml
nwdiag {
  // Group outside of network definitions
  group {
    color = "#FFFAAA";

    web01;
    web02;
    db01;
  }

  network external {
    web01;
    web02;
  }
  network internal {
    web01;
    web02;
    db01;
    db02;
  }
}
@enduml
```

<figure><img src="/files/tkl5fkwjdeJ5hp88lQMc" alt="" width="283"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.pranaypourkar.co.in/the-programmers-guide/system-design/system-design-methodology/diagrams/uml-diagrams/plantuml/network-diagram.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.