Actors: What, Why, and How (#161)
Donovan Preston bio
30min ◊◊ Intermediate
Saturday 02:15pm, Centennial III
categories:
concurrency, distributed system, eventlet, infrastructure, open source, rest, scaling, wsgi
Since the dawn of concurrency research, there have been two camps: shared everything, and shared nothing. Most modern applications use threads for concurrency, a shared everything architecture.
Actors, however, use a shared nothing architecture where lightweight processes communicate with each other using message passing. Actors can change their state, create a new Actor, send a message to any Actor it has the Address of, and wait for a specific kind of message to arrive in it's mailbox.
We will discuss the benefits of using the Actor architecture and strategies for implementing an Actor system in Python.
http://bitbucket.org/fzzzy/python-actors/
Actors, however, use a shared nothing architecture where lightweight processes communicate with each other using message passing. Actors can change their state, create a new Actor, send a message to any Actor it has the Address of, and wait for a specific kind of message to arrive in it's mailbox.
We will discuss the benefits of using the Actor architecture and strategies for implementing an Actor system in Python.
http://bitbucket.org/fzzzy/python-actors/
Files:
| file | size | uploaded | comment |
|---|---|---|---|
| Actors_PyCon_2010.pdf | 1.3 MB | Sat, Feb. 20th, 12:49 p.m. | Final slide deck |
| Actors_PyCon_2010_.pdf | 1.4 MB | Sat, Feb. 20th, 12:56 p.m. | Final slide deck without ugly white borders. |
video:
# Permalink
.