Speeding up Without Slowing down
summary
FT.com is one of the world’s fastest news sites and deploys to production every ten minutes, but that speed comes from concrete choices and trade-offs: a hundred microservices, a component library (Origami) with ~30 components per page, a Fastly-backed cache plus pre-flight header conversion that groups users for cache hits, and a paywall that runs in under 20 ms with a 200 ms timeout budget. A custom frontend layer called nui (CDN + build wrapper) fixes asset reuse but adds complexity and team friction.
AI-written summary · about
chapters (6)
- 0:00Start
- 7:48These practices free us to release quality software quickly, with confidence
- 23:30Performance is not a core front-end skill It's weird, complex and optional
- 24:06Empathy and experience is what enables you to choose the right abstractions for your application
- 27:21Weigh up the pros and cons for your whole team
- 28:11Work with your team to find the right balance
related talks
33mWeb performance in large-scale applications
45mSpeeding up Code, Webpages and Teams
42mChallenges for Developers of Building Large Web Applications
21mSlowing Down To Go Faster
45mFrontend Perfor
11mMaking Performance Personal at FT Labs
04mSimon Wistow (Fastly) interviewed at Fluent 2014
28mCSS and the Critical Path