Real-time Web Application with Socket.IO, Node.js, and Redis

From JSDC 2013

Transcript

1. Real-time Web Application with Socket.IO, Node.js, and Redis York Tsai, JSDC 2013
2. Who is York • http://www.linkedin.com/pub/york-tsai/13/bb/8a8 • https://twitter.com/yorktsai • https://www.facebook.com/yorktsai • VP Engineering @ EZTABLE
3. Never Live Demo! • http://jsdc.york.tw/ • I hope this work on my (and yours) computer ...
5. You may Have Heard About • Forever Iframe • XMLHttpRequest Long Polling • Cometd • Websocket • http://en.wikipedia.org/wiki/Comet_(programming ) • TL;DR
6. Socket.IO • Cross browser (including IE 6) • Real-time and bi-directional persistent connection (WebSocket) • Very simple to use • Javascript!
7. Start a Server
8. Sending and Receiving Events
10. Select Receivers for Events
11. Broadcasting
12. Rooms
13. Single Target
14. Multiple Applications?
15. Namespacing
16. How About New Connections?
17. Data Persistence • Need a persistence layer • Get data from the persistence layer whenever a new connection established
18. Integration I have component X,Y,Z want to send/receive data from user's browser
19. Pub/Sub or Message Queue Messaging system usually supports both
20. Pub/Sub Digram from Python's Website
21. Redis • Super-fast in-memory data structure server • Pub/Sub • Rich client libraries • Zero install and easy to operate
22. 3 Commands • SUBSCRIBE channel • UNSUBSCRIBE channel • PUBLISH channel message
23. In addition... • Connect multiple node.js server to one redis channel • Scalability!
24. Two Connections per Server
25. Redis-backed Pub/Sub • Two clients required: one for pub, one for sub • Use one channel, add metadata to your message
26. Redis-backed Pub/Sub
27. Frequently Asked Questions
28. SSL? Yes!
29. SSL Server
30. SSL Client
31. Cross domain? Yes! (If use WebSocket or JSONP)
32. Authentication?
33. Authentication • Cookie & Session • Cookie does not cross domain, use SSL + Access Token instead
34. Load Balancing? Yes! (If use Nginx >= 1.3.13)
35. Sample Nginx Configuration
36. Load Balancing using ELB • ELB (Elastic Load Balancer)'s HTTP(S) proxy does not understand websocket requests • Use TCP/SSL, instead of HTTP/HTTPS • No session stickyness • No X-Forwarded-For header
37. Scalability • Single thread • 2500~3500 connections per process • As many processes as you want
38. Configurations • store (default: MemoryStore, single process only) • transports (default: websocket, htmlfile, xhr- polling, jsonp-polling) • authorization (default: false)
39. Configurations - transports
40. Thank You! The slide is also the live demo itself. Please check the following repo! https://github.com/yorktsai/jsdc2013