Migrating Pinterest profiles to React
summary
Pinterest migrates profile pages piecewise to React using a node.js sidecar to enable isomorphic server rendering alongside Python Django and Nunjucks/ginger templates, bridges React into the old module system, and reuses the legacy API via HOCs. Scale is 175M monthly users and ~150k RPS; experiments run with Gatekeeper A/B tests and show up to 20% gains in DOM interactive and page views. Bottom-up migration avoids back-and-forth framework nesting and measures performance and engagement before full rollout.
AI-written summary · about
chapters (10)
- 0:00Introduction and goals
- 1:38Why migrate to React
- 4:11The hybrid migration strategy
- 6:11Overcoming migration challenges
- 9:03Infrastructure implementation
- 16:40Component bridge architecture
- 20:01Legacy resource management
- 22:02A/B testing and impact
- 26:49Post-migration benefits
- 28:31Q&A and future outlook
related talks
28mMigrating Pinterest profiles to React
25mMigrating Pinterest profiles to React
38mHow Pinterest switched their template rendering engine to React
19mPivoting to React, at scale
29mIncrementally Adopting GraphQL and Relay at Pinterest
21mMigrating critical apps to React
38mMigrating from PHP legacy code to React & Best Practices in React
10mHow to migrate 50,000 lines of code to React Server Components