9 anti-patterns for node.js teams
77 likes50,540 views
The document outlines nine anti-patterns for Node.js teams, emphasizing the importance of adapting to Node.js without the baggage of previous technologies. Key points include avoiding monolithic applications, using proper error handling, and embracing async programming patterns. Moreover, it encourages teams to leverage the Node ecosystem and community resources effectively.
9 anti-patterns for node.js teams
- 1. 9 anti-patterns for node.js teams Jeff Harrell @juxtajeff
- 2. Node first went live on paypal.com in 2013. Since: • 35 apps live (marketing, signup, account, payments, etc). • 400 new JavaScript engineers • 500,000 npm installs per day (internally) Made a good deal of mistakes to learn from
- 3. Anti-pattern #1 Baggage from your previous technology
- 4. • "Node doesn't support x. It won’t work" • “How do I deal with npm version conflicts?” • “Can’t let the app restart. It takes too long”
- 5. Leave your baggage behind." ! Except when you’re flying
- 6. Anti-pattern #2 Monolithic applications
- 7. • Use an internal npm instance • Publish modules vs. embedding functionality • Don’t overload modules – compose them Prefer different user, credit card and bank modules Avoid a single “shared” module
- 8. Build with many blocks, not one."
- 9. Anti-pattern #3 Googling “How to do x in JavaScript”
- 10. • jQuery results dominate search engines • Understand ES5 • Be aware of what’s coming in ES6
- 11. Learn JavaScript before diving in." !
- 12. Anti-pattern #4 Handling errors
- 13. • Use an Error object, not a string • Throwing is for programmer errors • Restart on uncaught exception vs ignoring it
- 14. Error cases are hard." ! Make sure to deal with them
- 15. Anti-pattern #5 Wrapping everything in promises
- 16. • Use for the right reasons (not throw or waterfall) • Modules should expose callback interfaces • Use promises sparingly in hot code 27% of CPU time spent in promise execution
- 18. Anti-pattern #6 Git URLs in your package.json
- 19. • Git URLs don’t fully leverage semver • Weird caching issues • Unstable state (akin to force overwriting in npm)
- 20. Publish to npm." ! Set it up internally and use it
- 21. Anti-pattern #7 Sloppy async code
- 22. • Understand control flow patterns • Don’t create crazy waterfalls Hoist functions Use promises (appropriately) Use async • Callback with code afterwards, but no return if (true) { callback(); } fallback();
- 23. Use good async patterns." ! Queue funny mis-ordered async sentence
- 24. Anti-pattern #8 Having node do everything
- 25. • SSL termination should be done by nginx • Heavy encryption is not for node • Don’t bind directly to port 80/443 “How do I enable gzip?” “How do I add an SSL cert to my app?”
- 26. Best tool, meet job." !
- 27. Anti-pattern #9 Ignoring the node ecosystem
- 28. • npm has a wealth of pre-written code • Get updates from community, e.g. Node Security • Conferences like this
- 29. Embrace your new community." ! Warning: May contain drama
- 30. Thanks!" ! Q&A is over drinks later!
- 31. Photo Credits 1. https://www.flickr.com/photos/11334694@N00/268023465/ 2. https://www.flickr.com/photos/14125773@N00/14205159881/ 3. https://www.flickr.com/photos/60364452@N00/3921008904/ 4. https://www.flickr.com/photos/83099438@N00/5902730038 5. https://www.flickr.com/photos/82402200@N00/523497824/ 6. https://www.flickr.com/photos/48553010@N00/113694992/ 7. https://www.flickr.com/photos/46889122@N03/4304137088/ 8. https://www.flickr.com/photos/39039882@N00/5189290606/ 9. https://www.flickr.com/photos/43145783@N00/1852428153/