Node @ flipkart
3 likes1,995 views
Node in Production at Flipkart Abhinav Rastogi discusses Node.js in production at Flipkart, covering challenges they faced like code maintainability, high availability, testability, and performance; why they chose Node like its parallel asynchronous nature and large ecosystem; and remaining challenges like relative newness and unsolved problems.
Node @ flipkart
- 1. Node @ Flipkart Abhinav Rastogi @_abhinavrastogi
- 2. !jQuery If you think jQuery is the answer, you lose a cookie and get an F grade!
- 5. Picking one is difficult! Plus its never exactly what you need
- 6. How we built a web stack in Node... It’s really not that difficult
- 7. Node in Production Now this is a different story altogether
- 8. Philosophy A web stack to build rich UIs for the next generation, embracing progressive enhancement.
- 9. Request Session API JSON Rendering Templates Response Cart API Search API Product API Promises HTML
- 10. Why Node? And that too in production? :O
- 11. Parallel, Async Huge benefit right there over conventional stacks
- 12. Light weight Best available JS execution env
- 13. Good community Buzzing like a beehive
- 14. “There’s a module for that” No, there really is.
- 15. Challenges we faced (So many of them!)
- 16. Code Maintainability What does it really mean?
- 17. Klass, Lodash For classy code B-)
- 18. High Availability As they say, 99.99% uptime guaranteed! But is it really?
- 19. Keep that process running Forever PM2 Shell Script!
- 20. Testability Ugh… test cases :(
- 21. Test it! Mocha, Chai, Istanbul
- 22. Performance So much to do… so little time
- 23. Profile it. Look, DTrace, Event Loop
- 24. Code Reusability Not just modules, but so much more now
- 26. Templating Jade, Handlebars, Underscore
- 27. ReactJS Does all that, and more
- 28. Write once, run anywhere! Sh*t... that sounds like Java
- 29. Rendering on Server Cacheable Reliable SEO friendly Optimised First Paint
- 30. Rendering on Client Less load on server Perceived Performance Rich UIs
- 31. Whoa.. easy there Logging Env specific code External HTTP requests
- 32. Responsiveness Useful? Needed? Required? Or just a fancy fad?
- 33. Cross-device/browser IE? Android 2.3? Cloud browsers? K.I.S.S!
- 34. Fanboyism? Close, but no :P
- 35. Why not Node? The other side of the story
- 36. Relatively new Many unsolved problems
- 37. “There’s a module for that” Its an Android Play Store… Not an Apple App Store
- 38. </3 Not for the weak-hearted
- 39. Productionizing Node Screw best practices. Whatever works is best.
- 40. Monitor and Alert! Nagios, Monit
- 42. Log it. Bunyan, Winston
- 43. Server Health and Rotation Status Keep the difference in mind!
- 44. QPS vs Concurrency Wait, aren’t they the same?
- 45. Recap
- 46. Node in Production Isomorphism Useful tools and modules