Concurrent programming is hard. Concurrent and distributed programming is even harder. But building web applications at scale demands your application to be concurrent and distributed.
Is there a way to make this easy and approachable?
The Actor Model tries to answer just that. It is based on the concept of small computational units communicating through asynchronous message passing, thus allowing concurrency and scalability while negating a lot of the problems of concurrent programming.
But up until now the actor model remained a rather niche approach and has not become a commonly used practice. This may change with the introduction of “Virtual Actors” – a new abstraction for writing distributed applications.
This abstraction was introduced with the Orleans framework by Microsoft and adopted to Java by EA with their Orbit framework.
In this session you will learn about the the Actor Model, what’s novel about Virtual Actors, and why it makes distributed application programming a lot simpler. We will also explore the idea of building a microservices architecture on top of Virtual Actors, including some practical lessons we learnt at Gigya doing just that.
rore
pyama86
kinocoboy2
tmokmss
ancaghenade
khmer495
twada
logiteca7
soutaro
masuda220
k0kubun
alli83
pangmoo
mojombo
geeforr
searls
colly
shpigford
tmm1
geoffreycrofte
lemiorhan
akmur
keithpitt
chrislema
csswizardry