Three-tier web service diagram
The classic split — web servers in the DMZ, application and database servers inside — drawn as an equipment layer with the services stacked on top.
Open this example in the editor →
The lower layer holds the internet router, firewall, L4 load balancer and the WEB, WAS and DB servers; the layer above holds Nginx, the order API and PostgreSQL in the same positions. Services are linked to their servers with "runs on", so selecting DB-01 and running impact analysis lights up the order database and the API that calls it.
Play the "Customer places an order" scenario to follow a request from router to firewall, VIP, WEB-01, Nginx, the API and the database, then on to the standby replica. For a proposal or handover document, copy a PNG from Export › Image.
What's on each layer
- L2 · Services — Customers (Internet), Web server (Nginx), Web server (Nginx), Order API (Tomcat), Order API (Tomcat), Order DB (PostgreSQL · primary), Order DB standby (streaming replica)
- L1 · Equipment — Internet router (2 ISP lines), Firewall (HA pair), L4 load balancer (VIP :443), WEB-01 (1U), WEB-02 (1U), Internal switch (10G), WAS-01 (2U), WAS-02 (2U), DB-01 (primary · 2U), DB-02 (standby · 2U), Backup storage (NAS 40TB)
- L0 · Server room — IDC floor 3, DMZ, Internal network
Flow scenario
Customer places an order
- Customers → Internet router — Customer opens the shop
- Internet router → Firewall — Arrives on the ISP line
- Firewall → L4 load balancer — 443 allowed
- L4 load balancer → WEB-01 — VIP sends it to WEB-01
- WEB-01 → Web server — Nginx receives
- Web server → Order API — Proxies /api/orders
- Order API → Order DB — Saves the order
- Order DB → Order DB standby — Replicated to standby
Good for
- System diagram for a new web service proposal
- Checking the blast radius before replacing a server
- Walking a new operator through the request path
Open this example in the editor →
More examples
- Disaster recovery (DR) pair diagramA primary site and a DR site side by side, with storage replication, database log shipping and the GSLB failover on one canvas.
- 42U rack elevationOne rack with ToR switches, a firewall, a management switch, DB and app servers, storage and a UPS — each placed at its U position.
- Network separation diagramA business network and an internet network kept apart: the internet only through VDI, files only through a cross-domain transfer server.