DevOps <3 node.js
1 like664 views
This document discusses why Node.js is a good choice for building scalable web applications. Node.js uses an event-driven, non-blocking I/O model that allows for highly scalable web servers. It also has a simple API based around callbacks and handles HTTP requests directly. Additionally, Node.js benefits from a large ecosystem of open source libraries and the npm package manager. The document provides examples of how Node.js can be used to build stateless, rapidly deployable servers and packages applications in a way that supports continuous deployment.
DevOps <3 node.js
- 1. DevOps <3 node.js github.com/miccolis | twitter.com/miccolis
- 2. SaaS DevOps @mapbox Not the kind of job where I expected to use javascript.
- 3. “Ah, right server side javascript” What is node.js again?
- 4. “Yea, cool so your front end devs can help, and you can use the same libraries, and probably even run all the same code on the server or the client, right? That’s great!” Everyone’s first response to node.js
- 5. No. Everyone’s first response to node.js is wrong.
- 7. <html> <head> <script src="jquery-1.2.6.min.js"></script> </head> <body> <script> $(document).ready(function(){ $("#mydiv").html("Hello World"); }); </script> <div id="mydiv"></div> </body> </html>
- 8. Most of that was DOM
- 9. $(document).ready() ...will be disregarded as just boilerplate.
- 10. It’s true, you can use the same libraries. They all expect async I/O
- 11. And build a framework where the application can run on the client or server! https://github.com/developmentseed/bones
- 12. YMMV
- 13. It’s not what most people expect, but there are good parts.
- 14. Async I/O Done the most simple way that could possibly work.
- 15. First class server support The node.js ‘hello world’ is a HTTP server, in 6 lines.
- 16. A package manager The best I’ve ever worked with.
- 17. The kinds of things that make my life easier.
- 18. Node.js & C10K 1. Event loop & non-blocking I/O 2. Simple & direct API; `callback(err, ...)` 3. ? 4. Profit
- 19. Node.js & HTTP • Any node.js program is a HTTP server (or could become one with trivial effort). • Your program is defined by its HTTP API, and can be tested as such. • Stateless, tested == rapidly deployable.
- 20. Node.js & NPM • Requires semantic versioning. • Completely captures dependencies. • Handles multiple instances of the same package with different versions. • Wildly inclusive.
- 21. In practice
- 22. Building servers • Lots of small projects • Scale independently • Varying lifecycles
- 23. Packaging • Every commit hits CI testing • Every commit is built into a deployable “slug” • Anything merged into `master` is considered production ready.
- 24. Streamlined deployment • Main client-side application is automatically deployed on every update to `master`. • Other applications can be deployed by any developer using a single CLI command.* * database cluster’s still require babysitting.
- 26. Because I need HTTP servers that scale... Why node.js?
- 27. ...and a strong open source community helping with libraries. Why node.js?