Caching strategies on https://dev.to
summary
DEV runs a read‑heavy Ruby on Rails site with over 1 million users and credits caching for its snappy pages. It shows Edge caching with Fastly (warm vs cold hits, shielding, purge API), fragment and browser caching for mixing static article shells with dynamic reaction widgets, and background counts via Counter Culture counter caching. Cache headers use smaxage and max‑age (smaxage 30 days, max‑age 3,000 days) and the team relies on purging rather than short expiries.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:17What is Dev.to
- 5:01Why caching is crucial
- 6:05Response caching fundamentals
- 7:53Where to implement caching
- 8:58Edge caching with Fastly
- 12:14Verifying Edge caching
- 13:16Cache control headers
- 14:43Counter caching
- 16:48Tag caching and queries
- 17:49When to implement caching
- 19:57Q&A
related talks
47mCaching strategies on https://dev.to
28mEdge Caching Dynamic Rails Apps
43mCache Me Outside - Caching Methodologies & Architectures
21mHigh Performance APIs through Caching
40mLiving on the Edge
38mThe power of cache in a slow world
24mCache for Commerce Performance and Optimization for High Volume Sales
56mCaching the uncacheable in Varnish