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
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.
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.