Integrating Node.js into an existing technology stack

Lots of companies have started experimenting with Node.js over the past year, but rather than re-writting everything they've integrated it into their existing stack where it fits best.

Transcript

1. Integrating Node.js into an existing technology stack
2. Andrew Nesbitt github.com/andrew @teabass
3. forwardtechnology.co.uk
4. I started and run the monthly London Node.js user group
5. I live a double life...
7. Benefits of Node Speed Many concurrent connections libraries like socket.io
8. Legacy Systems Can’t be re-written Already solving the problem to some degree
9. Benefits of integration Move faster on particular features Separation of concerns right tool for the right job Node isn’t great for everything
10. Let’s do this! I’ve got 7 different approaches for bringing node into your existing system Ranging from the sane and obvious to the wild and crazy
11. Separate tools
12. Url shorteners and redirection Command line tools Asset minification Pixel Trackers Internal tools Monitoring Chat bots pixel trackers - documentcloud (ping) monitoring - etsy (statsd) Nicely decoupled
13. Shared databases
14. Connect directly to MySQL, Postgres etc Share data with a key-value store Likely to duplicate domain logic May introduce race-conditions
15. Working with APIs
16. Linkedin Mobile Github Downloads Avoid duplication of domain logic
17. Producing APIs
18. Websocket Services Faye Ebay’s ql.io
19. Message Queues
20. ZeroMQ Resque Redis Pubsub dnode
21. Streams If you have a lot of data flowing through your application you might create a streaming API Node is great for both creating and consuming streams
22. Twitter, Facebook, Salesforce HTTP long polling Comet XMPP
23. Embedding Now we get to the more extreme
24. Ruby Racer Hadoop and timothy Android Sprintstack (previously rhinode) PLV8
25. create or replace function fib(n int) returns int as $$ function fib(n) { return n<2 ? n : fib(n-1) + fib(n-2) } return fib(n) $$ LANGUAGE plv8 IMMUTABLE STRICT;
26. http://pgeu-plv8.herokuapp.com Will Leinweber from Heroku
27. Summary
28. Take a unix-like approach Decoupled Systems Use APIs to share data Play to node’s strengths
29. Questions?