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.
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
| Name | Kind | Subnet | VLAN | Notes |
|---|---|---|---|---|
| DMZ | Zone | 10.10.0.0/24 | - | - |
| Web tier | Segment | 10.10.1.0/24 | 101 | - |
| App tier | Segment | 10.10.2.0/24 | 102 | - |
| Data tier | Segment | 10.10.3.0/24 | 103 | - |
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.
| Device | Type | Hostname | IP address | Role | Owner | Segment |
|---|---|---|---|---|---|---|
| Internet | Internet | - | - | - | - | - |
| CDN / WAF | CDN | - | - | - | Platform | - |
| Edge firewall | Firewall | fw-edge-01 | 10.10.0.1 | - | Network | DMZ |
| Load balancer | Load Balancer | lb-01 | 10.10.0.10 | Load Balancer | Platform | DMZ |
| Bastion | Terminal | bastion-01 | 10.10.0.20 | Jump Host | Platform | DMZ |
| web-01 | Server | web-01 | 10.10.1.11 | Web Server | Web team | Web tier |
| web-02 | Server | web-02 | 10.10.1.12 | Web Server | Web team | Web tier |
| app-01 | Server | app-01 | 10.10.2.11 | Application Server | App team | App tier |
| app-02 | Server | app-02 | 10.10.2.12 | Application Server | App team | App tier |
| Internal firewall | Firewall | fw-int-01 | 10.10.3.1 | - | Network | - |
| db-primary | Database | db-01 | 10.10.3.11 | Primary | Data team | Data tier |
| db-replica | Database | db-02 | 10.10.3.12 | Backup | Data team | Data tier |
| Backups | Backup | - | 10.10.3.20 | - | Data team | Data 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 freeOther templates
- Small office networkFirewall, a staff LAN, a server VLAN and isolated guest Wi-Fi - the classic single-site SMB layout.
- Hybrid cloudA head office joined to a cloud VPC by site-to-site VPN, with public and private subnets.
- Zero trust accessUsers reach private apps only through an identity-aware access proxy backed by SSO, device checks and a SIEM.
- Home labRouter, managed switch and three VLANs - home, lab and IoT - for documenting your own setup.