Kamaelia is generally a \"shared nothing\" architecture, but occasionally you *really* need to share data explicitly. When you do, you need to constrain how you share data and careful about how you advertise services. This is the first presentation done on the facilities that exist in Kamaelia to support this.
This presentation was given at Pycon UK 2008, Birmingham uk. Lots of good feedback was had during the q&a and an updated & improved version will be posted at some point in the relatively near future.
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...
Sharing Data and Services Safely in Concurrent Systems using Kamaelia
1. Sharing Data and Services Safely in
Concurrent Systems using Kamaelia
Michael Sparks (BBC Research)
http://edit.kamaelia.org/GetKamaelia
2. Unconstrained shared data* is
the cause of most problems in
concurrent systems
r
t ally o
*Ac ciden e
otherwis
Michael Sparks (BBC Research)
http://edit.kamaelia.org/GetKamaelia
3. Kamaelia therefore tries to
eliminate all shared data
... unless necessary
Michael Sparks (BBC Research)
http://edit.kamaelia.org/GetKamaelia
