Modern HTTP Architecture
summary
Argues for breaking a monolithic web app into small HTTP services so APIs deliver data and a thin HTML as a service layer renders pages, letting parts scale independently (example: a few million-record contributions DB causes bursts to tens of thousands of visitors). Recommends specific tools and patterns: nginx + varnish sandwich for SSL, proxying and caching, node for I/O tasks, Redis/memcached and Postgres/MySQL for stores, and sharing templates like mustache/handlebars; follows 12factor.net guidance.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:37Housekeeping
- 1:04Questions
- 1:49About me
- 2:07Architecture
- 2:26Expectations
- 2:55Theory
- 3:27Traditional Infrastructure
- 5:20Scaling
- 6:43The Texas Tribune
- 9:42One Application Server
- 10:23MultiDevice World
- 12:06UNIX Philosophy
- 18:18Modern HTTP Architecture
- 19:06Enterprise Ready
- 20:28ServiceOriented Architecture
- 22:11ORM
- 23:57GitHub
- 26:13Scaling Services
- 26:58Implementation Details
- 29:43HTML as a Service
- 34:40Wrapup
related talks
34mThe Internet is your Application Blueprint
37mBuilding the Hundred-Year Web Service with htmx
18mSoftware Architecture Building Better Applications with Architecture Best Practices
28mRequiem for APIs - The Evolution of Web Development
27mHTML Hypermedia APIs and Adaptive Web Design
01h 00mFrom Mosaic to Modern: The Evolution of Web App Architectures
39mMinimal Viable Architecture
23mIntegrating Web Apps