Migrating Pinterest profiles to React
summary
Migrating Pinterest profiles to React describes concrete choices and outcomes: introducing a node.js sidecar to render Nunjucks on the server, adding a Denzel→React bridge via a new component keyword, using HOCs to reuse the old resource layer, and running A/B experiments per page to measure impact. Results show up to 20% faster DOM Interactive and ~10% engagement lift, all achieved without changing UI designs while keeping development incremental and parallel.
AI-written summary · about
chapters (16)
- 0:00Start
- 3:16Large Developer Community
- 7:00Javascript rendering on the server-side
- 8:09Adapters for old data sources
- 8:40Web App Architecture
- 11:44Python Jinja Renderer (before)
- 12:51NodeJS Template Renderer (after)
- 16:24Denzel-React Bridge
- 17:17Reusing Server-Side HTML
- 18:06Higher-Order Components as Adapters
- 18:32Adapters for old resources
- 19:53A/B testing Framework
- 20:43Experiment setup
- 21:33Bottom up approach
- 22:11Experiment Dashboard Num Search Request
- 24:10Developer Experience
related talks
28mMigrating Pinterest profiles to React
45mMigrating Pinterest profiles to React
38mHow Pinterest switched their template rendering engine to React
19mPivoting to React, at scale
38mMigrating from PHP legacy code to React & Best Practices in React
31mDon't Rewrite, React!
21mMigrating critical apps to React
29mIncrementally Adopting GraphQL and Relay at Pinterest