How Pinterest switched their template rendering engine to React
summary
Pinterest replaces Django/Nunjucks server rendering by inserting a Node sidecar that runs Nunjucks so templates keep working while teams migrate them one subtree at a time to React. The site runs at ~175 million monthly users and ~150,000 requests/sec; the migration to the Node/Nunjucks architecture takes about six to seven months and completes, then iterative React rollouts show measurable wins — about 20% faster profile pages and ~30% gains on another flow — with instrumentation, linting rules, and experiments preventing regressions.
AI-written summary · about
chapters (6)
- 0:00Start
- 20:54Linters & Render-all Tests
- 24:28Experiment Dashboard
- 25:35TSDB Metrics
- 26:17Performance
- 31:20Developer community
related talks
45mMigrating Pinterest profiles to React
25mMigrating Pinterest profiles to React
28mMigrating Pinterest profiles to React
19mPivoting to React, at scale
31mReact on Rails
39mNavigating front-end architecture like a Neopian
21mMigrating critical apps to React
25mThe first two seconds: Faster page loads with React