Hybrid concurrency patterns
Download as KEY, PDF82 likes15,316 views
Kyle Drake discusses the transition from event-driven architectures like EventMachine to a more effective model using Celluloid, which combines threaded and reactor patterns for Ruby applications. He critiques EventMachine for its limitations and complexity, promoting the actor model as a more efficient alternative for handling concurrency. The document also highlights the potential for distributed objects and the development of related tools like DCell for Ruby.
Hybrid concurrency patterns
- 1. Threads and Events in Harmony with Celluloid Kyle Drake
- 2. Hi, I’m Kyle Drake. I work at Geoloqi Esri. We built a geofencing Text and real-time location streaming platform.
- 3. Last year, IText a did talk at KRTConf.
- 4. I was really into pure event-driven Text (reactor pattern based) architecture.
- 5. EventMachine, Twisted, Node.js • Event-driven Text • No threads • One CPU core • Process Spawning
- 6. I released sinatra-synchrony, so I could use Text EventMachine without callbacks.
- 7. Since then, I’ve Text changed my mind.
- 8. I’m really not a fan of EventMachine Text anymore.
- 9. EventMachine is • A frankenstein - guts the ruby internals • Not in active development Text • Makes non-blocking IO block • Requires special code from Ruby libraries • Hard to use in an OOP way • Is really difficult to work with • Poorly documented
- 10. Ruby developers need to stop using EventMachine. It’s Text the wrong direction.
- 11. Check this benchmark Text out:
- 13. Predictions: More Cores. A lot more.
- 14. Predictions: More libraries = more memory
- 15. Will process spawning work forever? It might.
- 16. It might not. Thousands of cores?
- 18. Ruby MRI: Global Interpreter Lock (single CPU core) Rubinius and JRuby: Full threading (multiple CPU cores) ~20KB per thread
- 19. We’re not finding a lot of thread safety issues in Ruby.
- 20. “Threading is hard”
- 21. Threading is not an intention!
- 22. Let’s fix it by abstracting threads into how humans think!
- 24. http://celluloid.io • Developed by Tony Arcieri • Actor Pattern for Ruby • Lots of inspiration from Erlang
- 25. Each actor is a concurrent object running in its own thread
- 28. First “Killer App”: Sidekiq Mike Perham
- 30. Don’t get me wrong. Event- driven is still awesome.
- 31. “..seasoned engineers are using a mix of threaded, event-based, and alternative concurrency approaches like Actors” - Alex Payne
- 32. What if we could combine threads and reactor patterns.. and actors?!
- 33. https://github.com/celluloid/celluloid-io • One reactor pattern per Celluloid object • Multiple reactors? No problem! • Doesn’t mess with code outside of actor • Utilizes all CPU cores (using JRuby and Rubinius) • Websockets, messaging systems, your hugely successful blog
- 34. You don't have to choose between threaded and evented IO!
- 36. "I thought of objects being like biological cells and/or individual computers on a network, only able to communicate with messages" - Alan Kay
- 37. Guess who was really into distributed network objects?
- 39. NeXT experimented with distributed objects in the mid 90s. NeXT was way ahead of its time.
- 40. "Objects can message objects transparently that live on other machines over the network, and you don't have to worry about the networking gunk, and you don't have to worry about finding them, and you don't have to worry about anything. It's just as if you messaged an object that's right next door." - Steve Jobs
- 42. https://github.com/celluloid/dcell • Objects talk over networks! • Uses 0MQ • Aware of eachothers’ existence • Distributed gossip protocol • Web UI • In the early stages, very promising
- 43. CODE EXAMPLES!
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n