Matthew Eernisse presented at NodeConf 2011 on best practices for running Node.js applications in production. Some of the key points discussed included organizing code for iterative development using an asynchronous and callback-based flow, relying on third-party modules from NPM which are improving but not yet perfect, assuming applications will fail and implementing error handling, measuring app performance with logging and metrics, and operating applications through communicative development and playing well with others.

1. Node.js in Production
Matthew Eernisse
NodeConf 2011

2. Who am I?
Matthew Eernisse
Work at Yammer
@mde on Twitter

3. Code organization

4. • Iterative development is easy
• Async, callback-based flow
• Third-party modules

5. App dependencies

6. • NPM is not there yet
• Third-party modules are not there yet
• Modify in-place, push patches back
• NPM, modules are improving

7. Assume you’re fucked

8. • Default condition is a preemptible error
• in-flight registry
• uncaughtException

9. Visibility, metrics

10. • Measure everything
• Log everything
• https://github.com/mikejihbe/metrics

11. Ops

12. • Communicative, consultative dev
• Ask what is expected
• Play nicely with others