Download as PDF, PPTX
Uploaded byRoss Kukulinski
Yodlr Realtime Technology Stack
The document outlines the technology stack used by Yodlr for real-time virtual presentations, emphasizing the use of WebRTC, Node.js, and Socket.IO. It details the architecture for managing audio streams and real-time connections and discusses considerations for scaling and database layers, including the use of MongoDB for long-term storage and Redis for real-time data. The author advocates for measuring performance and utilizing CI/CD practices in the development and deployment process.
More Related Content
Similar to Yodlr Realtime Technology Stack
Yodlr Realtime Technology Stack
- 1. @RossKukulinski WebRTC, Node.JS, and Socket.ioin Production Silicon Valley Realtime October 7, 2015
- 2. @RossKukulinski Ross Kukulinski Yodlr Founder/ CEO BayNode Organizer nodejs Evangelist Soccer Fanatic ross@getyodlr.com
- 3. @RossKukulinski Yodlr: Easy VirtualPresentations • Runs in your web browser • No plugins or downloads • HD voice chat • Audio recording • File sharing • PDF/Powerpoint presentations • Support for large meetings & webinars
- 4.
- 5. @RossKukulinski Our Tech Stack InfrastructureDatabase Server-Side Client-Side
- 6. @RossKukulinski Our Client-Side • WebRTC •Access to microphone & speaker via browser • Streams audio over network to our mixing service • Socket.io • Realtime connection to presence/chat/upload services • We only enable websocket protocol
- 7. @RossKukulinski Scaling WebRTC Media Imagecredit: Philipp Hancke
- 8. @RossKukulinski Scaling WebRTC Media Imagecredit: Philipp Hancke
- 9. @RossKukulinski Scaling WebRTC Media Imagecredit: Philipp Hancke
- 10.
- 11. @RossKukulinski Socket.io & NodeJS •Socket.io • “Real-time bidirectional event-based communication” • Built on top of websockets (can fall back to long-polling) • NodeJS • Excellent at maintaining many concurrent connections • But… Node is single threaded • Scale by running multiple instances of your application
- 12. @RossKukulinski Socket.io in Production •Enable sticky load balancing if using XHR Polling or JSONP Polling • Need a database layer if: • Broadcast messages between clients • Using built-in ‘rooms’ feature • Authentication • Authentication? • JSON Web Token (JWT) • Custom middleware functions
- 13. @RossKukulinski Socket.io Database • Defaultsto a memory-store • Redis is the ‘popular’ database store • Note: messages are NOT persistent • Other DB support by extending socket.io-adapter • socket.io-rethinkdb • socket.io-mongo last updated 2 years ago :(
- 14. @RossKukulinski Redis • Simple key/valuestore with pub-sub • Easy to setup and build with • FAST! • But… HA is a pain in the neck • Not really geared toward persistent/long-term storage
- 15. @RossKukulinski Our Database Layer •Long-term Storage: Mongodb • User accounts / Credentials / Permissions • Historical anonymized usage data • Temporary Storage: Redis • Realtime room data • Socket.io persistence layer
- 16.
- 17. @RossKukulinski Database with persistent storageAND pub-sub capability
- 18.
- 19. @RossKukulinski Our New TechStack? Infrastructure Database Server-side Client-Side
- 20. @RossKukulinski DBaaS or self-hosted •Mongodb hosted by ObjectRocket (Rackspace) • Redis self-hosted • In general: If you don’t have a DBA, go with a DBaaS
- 21. @RossKukulinski In an alternateuniverse… • Ditch socket.io for SaaS pub/sub/message system • e.g. PubNub, Firebase, Pusher • Might be lower TCO, but vendor lock-in concern
- 22. @RossKukulinski Realtime DevOps • Measureeverything • Statsd / Graphite / Grafana • Deploy early & often (CI/CD) • We LOVE Docker, Kubernetes, & CoreOS
- 23.