ruby + websocket + haproxy
Download as PPT, PDF0 likes2,040 views
This document summarizes the technology stack and use of websockets at oneplaylist.fm. The key aspects are: - The stack includes Ruby on Rails, Redis, EventMachine, HAProxy, Resque, MongoDB, CoffeeScript, and Elasticsearch. - HAProxy is used for TCP load balancing and handles HTTP as well, distributing traffic across multiple Rails app servers, Elasticsearch instances, and the EventMachine websocket server. - Websockets are handled via a TCP connection to the EventMachine server through a separate subdomain, keeping HTTP requests on the main app domain. - Redis is used for centralized communication and state management via Pub/Sub, with tokens mapping users to channels and event data pushed
ruby + websocket + haproxy
- 1. websocket on ruby oneplaylist.fm beta use case
- 2. The Stack • ruby on rails • redis • ruby-eventmachine • HA-Proxy
- 3. Other on Stack • Resque: background processing in rails • mongodb • coffeescript js heavy • elasticsearch (tire ruby gem)
- 4. HA-Proxy • tcp level load balancer • handle http level too • super fast, and so on..... • high availaibility made easy
- 5. HA-Proxy stack • HA-Proxy -> 3 ruby on rails front • HA-Proxy -> 3 elasticsearch instance (direct from coffee) • HA-Proxy -> event-machine tcp level websocket
- 6. HA-Proxy websocket • http://oneplaylist.fm -> app • http://oneplaylist.fm/websocket -> tcp event machine !! • same ip, same domain, sub path !!!!
- 7. Redis and websocket ? • handle stateless auth -> pass a token each request pass from front • redis is a central point of communication: super fast and performant • PUB SUB ! -> push to websocket
- 8. Redis and websocket • each token -> a user id • after authenticate, the eventmachine tcp session register to redis pub pipe with key user id • all message to user from rails -> pub redis key -> eventmachine redis -> websocket / browser in real time of course
- 9. Rails -> redis • Rails app write data in redis key before pushing • when user reconnect -> eventmachine make a get on key and push back to browser • some part of app are render only with webscoket data -> better consistency
- 10. more infos • http://oneplaylist.fm • https://twitter.com/mathieuel • http://www.mathieu-elie.net