N‑Tier (Client‑Server) Architecture

Multi-tier runtime architecture (e.g., presentation, application, data) where clients request services from servers across tiers.

Enabled By Platform Building Blocks

Enterprise Integration: Connects heterogeneous systems, supports ETL, and ensures interoperability.
Identity & Access Management: Provides authentication, authorization, and federation for all services.

What it is

A foundational distributed style evolving from 2‑tier to N‑tier deployments: presentation (UI), application/services, and data tiers communicate over a network.

Benefits

Simplicity and clear boundaries
Centralized control, security, and scaling
Ubiquitous across web and enterprise

Distinctions vs. Layered Architecture

N‑tier describes deployment/runtime tiers; layered describes code organization
Many systems use both: layered code deployed across N runtime tiers

Trade-offs

Server bottlenecks and single points of failure
State management and session handling
Latency sensitivity for chatty protocols