Secrets of a Node Team

The highs and lows a node.js agency

Transcript

1. SECRETS OF A NODE TEAM The highs and lows a node.js agency
2. PAUL SERBY CTO of Clock @serby
3. IDEAS + CRAFT
4. we make websites
5. do you code?
6. WHY NODE
7. WHY NODE ‣ 10 years doing PHP
8. WHY NODE ‣ 10 years doing PHP ‣ Waited 3 years for PHP 6
9. WHY NODE ‣ 10 years doing PHP ‣ Waited 3 years for PHP 6 ‣ Frameworks V2.0 starting to appear
10. WHY NODE ‣ 10 years doing PHP ‣ Waited 3 years for PHP 6 ‣ Frameworks V2.0 starting to appear ‣ Blocking IO was consistently our main bottleneck at scale
11. WHY NODE ‣ 10 years doing PHP ‣ Waited 3 years for PHP 6 ‣ Frameworks V2.0 starting to appear ‣ Blocking IO was consistently our main bottleneck at scale ‣ Bored of PHP
13. SUN PERKS 154,359 Registrations Ran for 3 months Peaking at 250 entries per second
14. SUN PERKS - PROFIT 40%
15. PAIN NPM version mis-match
16. PAIN NPM version mis-match SOLUTION
17. PAIN NPM version mis-match Check node_modules packages into GIT http://www.futurealoof.com/posts/nodemodules-in-git.html SOLUTION
19. npm rebuild
20. PROPER SOLUTION
21. PROPER SOLUTION npm shrinkwrap
22. PROPER SOLUTION npm shrinkwrap npm install --save
23. PROPER SOLUTION npm shrinkwrap npm install --save npm install --save && npm shrinkwrap
24. Semantic Versioning 2.0.0
25. Semantic Versioning 2.0.0 MAJOR . MINOR . PATCH
26. Semantic Versioning 2.0.0 MAJOR . MINOR . PATCH MAJOR version when you make incompatible API changes
27. Semantic Versioning 2.0.0 MAJOR . MINOR . PATCH MAJOR version when you make incompatible API changes MINOR version when you add backwards-compatible functionality
28. Semantic Versioning 2.0.0 MAJOR . MINOR . PATCH MAJOR version when you make incompatible API changes MINOR version when you add backwards-compatible functionality PATCH version when you make backwards-compatible bug fixes
29. Semantic Versioning 2.0.0 MAJOR . MINOR . PATCH MAJOR version when you make incompatible API changes MINOR version when you add backwards-compatible functionality PATCH version when you make backwards-compatible bug fixes http://semver.org
30. PAIN
31. PAIN I don’t know how to build big applications
32. Most modules should have exactly 1 export. Module systems should be designed around that use case first, not for dozens of exports. substack if your module exposes more than one function, you might be doing it wrong :) mikeal
33. Coincidental Logical Temporal Procedural Communicational Sequential Functional COHESION WORST BEST
34. IDEs vs Text Editors 2010 2013 95% 10% 5% 90% IDEs Editors
35. SEPARATION
36. SEPARATION ‣ Craft your application by combining modules
37. SEPARATION ‣ Craft your application by combining modules ‣ Build as many applications as you need
38. SEPARATION ‣ Craft your application by combining modules ‣ Build as many applications as you need ‣ Your web server is a web server it’s not a: CSS compiler, JavaScript compiler, Message queue, Email dispatcher, Certainly not cron!
39. SEPARATION ‣ Craft your application by combining modules ‣ Build as many applications as you need ‣ Your web server is a web server it’s not a: CSS compiler, JavaScript compiler, Message queue, Email dispatcher, Certainly not cron! ‣ Ensure your applications and processes can talk to each other
40. two years later
41. LOAD BALANCER CDN WEB SITE REST API TEMPORAL AGENTS (CRON) CMS ADMIN REST API WORKERS NPM APPS DOMAIN SERVICES 3rd PARTY MODULES PROJECT MODULES
42. LOAD BALANCER CDN WEB SITE REST API TEMPORAL AGENTS (CRON) CMS ADMIN REST API WORKERS APPS MESSAGE BUS (0MQ)
43. MAY 2013
45. JUNE 2013
46. AUGUST 2013
47. SUN PERKS - PROFIT 33%
48. PAIN
49. PAIN ‣ NPM isn’t always available
50. PAIN ‣ NPM isn’t always available ‣ NPM can be slow
51. PAIN ‣ NPM isn’t always available ‣ NPM can be slow ‣ No SLA
52. PAIN ‣ NPM isn’t always available ‣ NPM can be slow ‣ No SLA ‣ Deployments depend on NPM
53. PAIN ‣ NPM isn’t always available ‣ NPM can be slow ‣ No SLA ‣ Deployments depend on NPM ‣ Some of our code needs to be private
54. PAIN ‣ NPM isn’t always available ‣ NPM can be slow ‣ No SLA ‣ Deployments depend on NPM ‣ Some of our code needs to be private ‣ ‘npm update’ doesn’t work with git URLs
55. SOLUTION
56. SOLUTION Private NPM Repo
57. SOLUTION Private NPM Repo http://clock.co.uk/tech-blogs/how-to-create-a-private-npmjs-repository
58. JOY
59. JOY browserify
60. PAIN
61. PAIN MEMORY LEAKS
62. SOLUTION
63. SOLUTION ‣ Learn the tools
64. SOLUTION ‣ Learn the tools ‣ dtrace / Manta
65. SOLUTION ‣ Learn the tools ‣ dtrace / Manta ‣ heap-dump - https://github.com/bnoordhuis/node-heapdump
66. SOLUTION ‣ Learn the tools ‣ dtrace / Manta ‣ heap-dump - https://github.com/bnoordhuis/node-heapdump ‣ Assume there are always memory leaks
67. SOLUTION ‣ Learn the tools ‣ dtrace / Manta ‣ heap-dump - https://github.com/bnoordhuis/node-heapdump ‣ Assume there are always memory leaks ‣ Monitor memory
68. SOLUTION ‣ Learn the tools ‣ dtrace / Manta ‣ heap-dump - https://github.com/bnoordhuis/node-heapdump ‣ Assume there are always memory leaks ‣ Monitor memory ‣ Make sure your application restarts quickly
69. SOLUTION ‣ Learn the tools ‣ dtrace / Manta ‣ heap-dump - https://github.com/bnoordhuis/node-heapdump ‣ Assume there are always memory leaks ‣ Monitor memory ‣ Make sure your application restarts quickly ‣ Restart your application nightly
70. is node.js any good?
71. thanks