Groovy Actors

Refreshed my link with Gerald “tensegrity” de Jong, triggered by a blog entry from TED titled Creatures on the beach from the Dutch sculptor Theo Jansen which instantly reminded me of Gerald’s Fluidiom and Darwin at Home projects.

Gerald’s email signature also mentioned Groovy Actors:

In a nutshell it’s a natural next step, building further on object-oriented programming (OOP), where objects become active talkative peers.
Imagine running thousands of concurrent programs on one computer where each program instance represents something or someone in the real world. Some things are passive and only react to events but lots of real world things also take initiative.
That’s why parts of this kind of system can better be represented in software by “autonomous agents” or “actors” which frequently interact with each other.

And built using the Groovy language.

Just wondering why Groovy Actors are limited to a single computer rather than autonomous peers distributed across thousands of computers. Love to have concepts from Erlang and JavaSpaces built in.

Love to see the Groovy Actors’ Hello Storage example implement the story of The Wizard, The Rabbit, and The Treasurer.

Author: Martien van Steenbergen

Martien is a Visioneer and touched by software.
people | software | happiness

One thought on “Groovy Actors”

  1. It’s not limited to a single host, although peer-to-peer communication is many orders of magnitude faster when they’re together. The unique beauty of these autonomous actors (handling persistence) is that they can pack up and move from one host to another when they choose to do so.

Leave a Reply