Modern Web Systems
Follow a systems-level path from DNS and HTTP through browser execution, rendering, frontend architecture, and backend boundaries.
Personal learning atlas by Tran Trong Thuc · About this Atlas · Atlas last updated Sep 22, 2026
This page is an orientation layer over canonical concepts. Embedding the path does not itself mark those concepts as covered; coverage comes only from substantive authored content elsewhere in the Atlas.
Modern Web Systems
Build a systems-level mental model of how browsers, protocols, rendering, frontend architecture, and backend boundaries fit together.
- Audience
- Software engineers who want to reason across the full web request and rendering path rather than learn one framework in isolation.
- Target depth
- reason
14 / 16 concepts currently covered
Outcomes
- Trace a request from DNS and TLS through the browser and application boundary.
- Compare major rendering and frontend data-loading approaches by constraints and trade-offs.
- Recognize where caching, browser security, and backend API design influence web behavior.
Path
DNS Resolution
Target depth: reasonAvailable Atlas content
HTTP Request Lifecycle
Target depth: operateAvailable Atlas content
TLS and HTTPS
Target depth: reasonAvailable Atlas content
Browser Runtime
Target depth: reasonNo Atlas content yet
Browser Event Loop
Target depth: reasonAvailable Atlas content
Browser Rendering Pipeline
Target depth: reasonNo Atlas content yet
Same-Origin Policy and CORS
Target depth: reasonAvailable Atlas content
HTTP Caching
Target depth: reasonAvailable Atlas content
CDN Behavior
Target depth: reasonAvailable Atlas content
CSR, SSR, and SSG
Target depth: reasonAvailable Atlas content
Hydration
Target depth: reasonAvailable Atlas content
Frontend Data Fetching
Target depth: reasonComponent Boundaries
Target depth: reasonAvailable Atlas content
- Component Boundaries: Make Ownership and Interfaces Explicit
- De-Overengineering the Frontend: Remove Accidental Architecture
- Incremental Frontend Migration: Strangler Patterns, Compatibility Boundaries, and Cutovers
- React Modernization: Upgrade Without Rewriting the App
- Modernizing a Seven-Year-Old React Application
- Frontend Modernization Decision Guide: Upgrade, Replace, Wrap, or Delete?
Frontend Bundle Performance
Target depth: reasonBackend Request Lifecycle
Target depth: operateAvailable Atlas content
API Design
Target depth: operateAvailable Atlas content