Hybrid concurrency patterns

1.
Threads and Events in Harmony with Celluloid Kyle Drake
2.
Hi, I’m KyleDrake. I work at Geoloqi Esri. We built a geofencing Text and real-time location streaming platform.
3.
4.
I was reallyinto pure event-driven Text (reactor pattern based) architecture.
5.
EventMachine, Twisted, Node.js • Event-driven Text • No threads • One CPU core • Process Spawning
6.
7.
8.
9.
EventMachine is • Afrankenstein - 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 difﬁcult to work with • Poorly documented
10.
11.
12.
13.
14.
15.
16.
18.
Ruby MRI: Global InterpreterLock (single CPU core) Rubinius and JRuby: Full threading (multiple CPU cores) ~20KB per thread
19.
20.
21.
22.
Let’s ﬁx itby abstracting threads into how humans think!
24.
25.
Each actor isa concurrent object running in its own thread
28.
30.
31.
“..seasoned engineers are usinga mix of threaded, event-based, and alternative concurrency approaches like Actors” - Alex Payne
32.
What if wecould combine threads and reactor patterns.. and actors?!
33.
https://github.com/celluloid/celluloid-io • One reactorpattern 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.
35.
36.
"I thought ofobjects being like biological cells and/or individual computers on a network, only able to communicate with messages" - Alan Kay
37.
Guess who wasreally into distributed network objects?
39.
NeXT experimented with distributed objects in the mid 90s. NeXT was way ahead of its time.
40.
"Objects can messageobjects 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 ﬁnding 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
41.
42.
https://github.com/celluloid/dcell • Objectstalk over networks! • Uses 0MQ • Aware of eachothers’ existence • Distributed gossip protocol • Web UI • In the early stages, very promising
43.
44.
45.

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

Hybrid concurrency patterns

More Related Content

What's hot

Similar to Hybrid concurrency patterns

Recently uploaded

Hybrid concurrency patterns

Editor's Notes