Back to front - Backend technologies for the frontend developer
summary
Argues front-end engineers must know concrete backend mechanics: servers set expiry headers and Cache-Control (use max-age, stale-if-error) so CDNs can cache product images for a day and profile pictures for minutes; use ETags to validate freshness and avoid full downloads; auth uses JWT access + refresh tokens to rotate credentials; transactional idempotency is solved with client-generated UUIDs so retries don’t double-charge (real-world food-delivery triple-order bug cited); deployments run in containers (Docker/containerd) on Kubernetes clusters with multi-region, load balancers and multi-primary DB replication; Chaos Monkey stresses resilience.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 2:33Caching fundamentals and strategies
- 9:39E tags and caching nuances
- 13:49CDNs and multi-layer caching
- 18:45REST API design principles
- 24:06JWT and OAuth basics
- 30:30Idempotency in transactions
- 36:12Service topology and containers
- 47:01Q&A and resources
related talks
27mFundamentals of Front End Ops
29mUX is frontend only! Why do I, super ninja backend developer, need to care about it?
01h 10mThe Future of Frontend Panel
08mWhen Worlds Collide: Frontend vs Database
38mThe Front-End Future
39mScaling Frontend Development
30mOld Gods & New: A Vision of Backend & Frontend
13mMicro Frontends Without Chaos: Architecture That Survives Scale