1.
Threads and Events inHarmony with Celluloid Kyle Drake

2.
Hi, I’m Kyle Drake. Iwork at Geoloqi Esri.We built a geofencing Textand real-time location streaming platform.

3.
Last year, IText a didtalk at KRTConf.

4.
I was really intopure event-driven Text(reactor patternbased) architecture.

5.
EventMachine, Twisted, Node.js• Event-driven Text• No threads• One CPU core• Process Spawning

6.
I releasedsinatra-synchrony,so I could use TextEventMachinewithout callbacks.

7.
Since then, I’ve Textchanged my mind.

8.
I’m really not a fanof EventMachine Textanymore.

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 developersneed to stop usingEventMachine. It’s Textthe wrongdirection.

11.
Check thisbenchmark Textout:

12.
Texthttp://rhaas.blogspot.com/2012/04/did-i-say-32-cores-how-about-64.html

13.
Predictions:More Cores.A lot more.

14.
Predictions:More libraries =more memory

15.
Will processspawning work forever? It might.

16.
It might not.Thousands of cores?

17.
Ruby MRI:Global Interpreter Lock (single CPU core) Rubinius and JRuby: Full threading (multiple CPU cores)~20KB per thread

18.
We’re not finding a lot of thread safety issues in Ruby.

19.
“Threading is hard”

20.
Threading is not an intention!

21.
Let’s fix it by abstractingthreads into how humans think!

22.
http://celluloid.io• Developed by Tony Arcieri• Actor Pattern for Ruby• Lots of inspiration from Erlang

23.
Each actor is aconcurrent objectrunning in its own thread

24.
First “Killer App”: Sidekiq Mike Perham

25.
Don’t get mewrong. Event-driven is still awesome.

26.
“..seasoned engineers areusing a mix of threaded,event-based, andalternative concurrencyapproaches like Actors” - Alex Payne

27.
What if we couldcombine threads and reactor patterns.. and actors?!

28.
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 hugelysuccessful blog

29.
You dont have tochoose between threaded and evented IO!

30.
Let’s getdistributed.

31.
"I thought of objects being like biological cells and/or individual computers on a network, only able to communicate with messages" - Alan Kay

32.
Guess who was really into distributed network objects?

33.
NeXT experimented with distributedobjects in the mid 90s.NeXT was way ahead of its time.

34.
"Objects can message objects transparentlythat live on other machines over the network, and you dont have to worry about thenetworking gunk, and you dont have to worry about finding them, and you dont have to worry about anything. Its just as if you messaged an object thats right next door." - Steve Jobs

35.
“Portable Distributed Objects”

36.
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

37.
CODEEXAMPLES!

38.
Help UsBuild This!

39.
Thanks! @kyledrakekyledrake.net