3 ms·
Those are both solid choices for servers. However neither of them have a scalability model suitable for HTTP/2 or WebSockets. That's something I wanted to try a
by ioquatix 6y ago
Those are both solid choices for servers. However neither of them have a scalability model suitable for HTTP/2 or WebSockets. That's something I wanted to try and address.
- nitrogen 6y agoI used EventMachine a lot about 8-10 years ago. I'm excited to see Ruby getting some concurrency love again. What are the goals and improvements of your underlying design in general, and especially those that make HTTP2 and WebSockets work?
- ioquatix 6y agoLight weight event driven tasks are very important. I outline some of the key improvements in this talk: https://www.youtube.com/watch?v=Dtn9Uudw4Mo https://www.youtube.com/watch?v=Dtn9Uudw4Mo
- timdorr 6y agoAnd thank you for addressing it, Samuel! I converted the streaming and Autopark clients in the Tesla API gem from EM to Async and has been great: https://github.com/timdorr/tesla-api/blob/master/lib/tesla_api/stream.rb https://github.com/timdorr/tesla-api/blob/master/lib/tesla_a... No more globals, which makes it much safer to use inside of threaded job runners like Sidekiq.
- ioquatix 6y agoIt would be awesome to talk about your work in a blog post, do you think you can reach out to me to explain your work in more detail?