Download as PDF, PPTX
Uploaded byRyan Burgess
Migrating a large codebase to Node & React
The document discusses the migration of a large codebase to Node.js and React at Netflix, emphasizing the benefits of faster innovation, improved developer productivity, and the ability to handle UI rendering efficiently. It outlines the migration strategy, which included tackling changes in sections rather than all at once and utilizing metrics to guide decisions. Key lessons learned include the complexity of estimating migration efforts and the importance of choosing appropriate technologies for the team.
More Related Content
Similar to Migrating a large codebase to Node & React
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Migrating a large codebase to Node & React
- 1. Migrating a large codebaseto Node & React Ryan Burgess @burgessdryan
- 2. What is yourreaction to migrating to a new codebase?
- 4. Once the migrationstarts it can be daunting
- 6. It doesn’t needto be that frustrating
- 7.
- 8. Software Engineer Managerat Netflix @burgessdryan
- 11. Why migrate toa new codebase? Why React & Node? How did we tackle the migration at Netflix? What lessons did we learn?
- 12. Why migrate toa new codebase?
- 13. The ability toinnovate faster
- 14. Simplify & separateconcerns
- 15.
- 16.
- 17. Our UI teamis familiar with JavaScript
- 18.
- 19. Great tooling inthe Node.js ecosystem
- 20. Allows for universalrendering of UI components
- 21. Makes development faster andincreases productivity
- 22. We use Restifyat Netflix Lightweight Absolute control over interactions with HTTP Automatic DTrace support https://github.com/restify/node-restify
- 23.
- 24. Why not anyof these other frameworks?
- 25. React supports universalrendering
- 26.
- 27.
- 28. Unified our markupwith corresponding view logic
- 30.
- 31.
- 32. How we tackledthe migration at Netflix
- 33. Decouple design changesfrom architecture changes
- 34. Don’t try tomigrate all at once, tackle in sections
- 35. Allows for flexibilityand ability to learn
- 36. Allowed us topivot Before leveraging React we used Dust.js https://github.com/linkedin/dustjs
- 37. Plan to supporttwo codebases
- 38. Leverage metrics • Atlasmetrics • A/B test metrics
- 39.
- 40.
- 41.
- 42.
- 43. Metric cycle Push toproduction Check metricsInvestigate / Iterate
- 44. What lessons did welearn?
- 45. Estimating a migrationis hard
- 46. Choose a technologythat works for you and your team
- 47. Migrate in sections,not all at once
- 48. Design changes canimpact your metrics
- 49. Use metrics wheneverpossible
- 51.