← Archyscape

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 →

L2 · ServicesCustomersInternetWeb serverNginxWeb serverNginxOrder APITomcatOrder APITomcatOrder DBPostgreSQL · prim…Order DB stan…streaming replicaL1 · EquipmentInternet rout…2 ISP linesFirewallHA pairL4 load balan…VIP :443WEB-011UWEB-021UInternal swit…10GWAS-012UWAS-022UDB-01primary · 2UDB-02standby · 2UBackup storageNAS 40TBL0 · Server roomIDC floor 3DMZInternal network
Layer by layer

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

Flow scenario

Customer places an order

  1. Customers → Internet router — Customer opens the shop
  2. Internet router → Firewall — Arrives on the ISP line
  3. Firewall → L4 load balancer — 443 allowed
  4. L4 load balancer → WEB-01 — VIP sends it to WEB-01
  5. WEB-01 → Web server — Nginx receives
  6. Web server → Order API — Proxies /api/orders
  7. Order API → Order DB — Saves the order
  8. Order DB → Order DB standby — Replicated to standby

Good for

Open this example in the editor →

More examples