UI @ Flipkart: A Node Direction
summary
Flipkart builds a custom Node/Express/ReactJS stack after five to six months, claiming server and client rendering with isomorphic JavaScript, sending JSON and templates together and caching HTML for SEO and perceived speed. Evaluation finds over 30 to 40 server-side JS frameworks, so a bespoke framework wins. Ops use forever/pm2 then switch to a tiny shell respawn script with taskset; profiling uses mocha and chai for tests, Istanbul for coverage, look/dce and toobusy for event‑loop CPU profiling. Migration proceeds incrementally and shows positive early results.
AI-written summary · about
chapters (17)
- 0:00UI at Flipkart
- 1:02Moving from jQuery/PHP
- 2:49Node.js frameworks
- 3:50Custom Node.js stack
- 4:53Node.js production challenges
- 8:22Code maintainability
- 10:49High availability in Node.js
- 14:00Testing Node.js apps
- 15:47Performance profiling
- 17:32Node.js event loop
- 19:18Code reusability server/client
- 21:02React.js isomorphic rendering
- 23:10Isomorphism challenges
- 24:33Responsiveness across devices
- 26:17Node.js risks and limits
- 27:59Node.js monitoring and logging
- 30:07Q&A
related talks
27mScaling NodeJS beyond the ordinary
39mNavigating front-end architecture like a Neopian
21mBuilding a Progressive Web App
22mPanel Discussion
47mJavaScript
45mBuilding Isomorphic Apps (Updated)
13mSpeed at Scale: Optimizing The Largest CX Platform Out There
46mArchitecture of a Modern Enterprise Node js Application