Three-tier web application architecture diagram

A classic three-tier web application: a CDN and edge firewall in front, a load balancer in the DMZ, then separate web, application and data tiers, each on its own subnet and VLAN.

Connections are labelled with their protocol and port (HTTPS 443, HTTP 8080, gRPC 9000, PostgreSQL 5432), so the diagram doubles as a record of which traffic is allowed between tiers.

Use this template freeIn the editor: File → New from template → Three-tier web application
DMZ10.10.0.0/24Web tier10.10.1.0/24 · VLAN 101App tier10.10.2.0/24 · VLAN 102Data tier10.10.3.0/24 · VLAN 103InternetCDN / WAFEdge firewall10.10.0.1Load balancer10.10.0.10Bastion10.10.0.20web-0110.10.1.11web-0210.10.1.12app-0110.10.2.11app-0210.10.2.12Internal firewall10.10.3.1db-primary10.10.3.11db-replica10.10.3.12Backups10.10.3.20
The template as it opens in Schema: 13 devices, 4 zones and segments, 12 connections.

How it's laid out

  • The data tier sits behind a second, internal firewall. A database is two firewalls away from the Internet.
  • Web and application servers come in pairs behind the load balancer. The primary database replicates to a replica, which is backed up nightly.
  • A bastion host in the DMZ is the administrative entry point.

Networks and segments

NameKindSubnetVLANNotes
DMZZone10.10.0.0/24--
Web tierSegment10.10.1.0/24101-
App tierSegment10.10.2.0/24102-
Data tierSegment10.10.3.0/24103-

Device inventory

In Schema this table isn't a separate document. It's generated from the diagram, can be edited in place, and exports as CSV.

DeviceTypeHostnameIP addressRoleOwnerSegment
InternetInternet-----
CDN / WAFCDN---Platform-
Edge firewallFirewallfw-edge-0110.10.0.1-NetworkDMZ
Load balancerLoad Balancerlb-0110.10.0.10Load BalancerPlatformDMZ
BastionTerminalbastion-0110.10.0.20Jump HostPlatformDMZ
web-01Serverweb-0110.10.1.11Web ServerWeb teamWeb tier
web-02Serverweb-0210.10.1.12Web ServerWeb teamWeb tier
app-01Serverapp-0110.10.2.11Application ServerApp teamApp tier
app-02Serverapp-0210.10.2.12Application ServerApp teamApp tier
Internal firewallFirewallfw-int-0110.10.3.1-Network-
db-primaryDatabasedb-0110.10.3.11PrimaryData teamData tier
db-replicaDatabasedb-0210.10.3.12BackupData teamData tier
BackupsBackup-10.10.3.20-Data teamData tier

Rules it checks

The template comes with these rule packs switched on. Schema checks them as you edit and marks anything that breaks a rule on the canvas. Every rule can be edited, turned off or deleted.

Perimeter & segmentation

Internet-facing systems sit behind a firewall, databases aren't exposed directly, and traffic between networks passes a firewall.

  • Internet-connected servers must sit behind a firewall
  • Databases must not connect directly to the Internet
  • Storage must not connect directly to the Internet
  • Servers reaching across a network boundary need a firewall in the path
  • Databases reaching across a network boundary need a firewall in the path
  • Workstations must not connect directly to databases

Documentation completeness

Every server, database and network device has the fields someone on call at 3am will need: an address, an owner, a role.

  • Servers must have an IP address
  • Servers must have an owner
  • Servers must have a role
  • Servers must record their OS
  • Databases must have an IP address
  • Databases must have an owner
  • Firewalls must have an IP address
  • Routers must have an IP address

Resilience basics

Nothing important hangs off a single link, databases have somewhere to back up to, and nothing is left unconnected.

  • Firewalls should have at least two connections
  • Routers should have at least two connections
  • Databases should have a backup target in their path
  • Production servers should record their criticality
  • Servers shouldn't be left unconnected

Start from this template

Open it in Schema, replace the example addresses with yours, and you have a diagram, an inventory and a written report of your network. Free during early access.

Use this template free

Other templates