How to make operations love Nodejs Apps
One little typo for Dev-kind, one big failure for Ops
(or vice versa if that makes more sense)
One little typo, is all what it takes to break a nodejs program. From an operational side, this doesn't give you much confidence.
Much of the documentation on nodejs out there is focused on building websites with Express and the Secret Sauce 'Socket.IO' and friends. Documentation on non-functional aspects, is sparse and more fragmented.
In this session I'd like to explore ways to improve your code to make it a joy to run it in production:
var aspects_covered = { error handling, logging, hardening, versioning, security, testing, packaging, deployment , monitoring, metrics, scaling, tuning ,debugging } ;
- We will center around a typical nodejs app (Express, SocketIO, Redis) , but many of the aspects hold true for other languages.
- So even if you are not a node-fan, you can pick up some ideas to apply in your <3-language
- Be warned, there might some sprinkles of #devops in there