Course contentsShow
← Cloud and Infrastructure
Lesson 183 of 2,9894. Cloud Networking BasicsFree lesson

Multi-Tier Network Architecture

Understand common patterns like web/app/database tiers using multiple subnets.

Multi-Tier Network Architecture

You'll learn: How to organize cloud networks into separate layers (web, app, database) using multiple subnets for security and scalability.

What is Multi-Tier Architecture?

Multi-tier architecture is a design pattern that separates your application into distinct layers, each running in its own subnet. Think of it like a restaurant: the dining room (web tier) faces customers, the kitchen (app tier) prepares orders, and the storage room (database tier) holds ingredients. Each area has different access rules and security needs.

Common Three-Tier Pattern

The most popular pattern uses three layers:

Web Tier (Public Subnet)

  • Hosts web servers and load balancers
  • Has internet access through route tables
  • Public-facing, receives user requests
  • Example: 10.0.1.0/24

Application Tier (Private Subnet)

  • Runs business logic and application servers
  • Receives requests only from web tier
  • No direct internet access
  • Example: 10.0.2.0/24

Database Tier (Private Subnet)

  • Stores persistent data
  • Accepts connections only from app tier
  • Most restricted access
  • Example: 10.0.3.0/24

Why Use Multiple Subnets?

Each tier gets its own subnet with dedicated route tables and security rules. If hackers breach your web tier, they still can't directly access your database because it's isolated in a different subnet. Traffic flows in one direction: web → app → database.

You can also scale each tier independently. Need more web servers? Add them to the web subnet without touching your database configuration.

Key Takeaway: Multi-tier architecture uses separate subnets for each application layer, improving security through isolation and enabling independent scaling of each tier.