Application and API Patterns
This part applies the pattern language to common customer and integration entry points. It separates web experience responsibilities from API platform responsibilities while showing where they work together.
What You Will Learn
Trace requests from edge controls through runtimes and data.
Choose hosting, scaling, deployment, and observability patterns.
Design API gateways, contracts, authorization, quotas, and lifecycle controls.
Recognize where web and API concerns overlap without collapsing them.
Chapters
Web Application Architecture — compose edge, application, data, security, scaling, and operating responsibilities.
API Platform Architecture — design governed API entry, contracts, backends, consumer controls, and observability.
How the Chapters Connect
The web chapter follows the complete customer request path. The API chapter then focuses on the managed contract between consumers and backend capabilities, making the boundary reusable across applications.