A typed actor has two parts—a publicly defined interface, and secondly, an implementation of the interface. Calls to the publicly defined interface are delegated asynchronously to the private instance of the implementation. In effect, the public interface provides the service contract that bridges the Actor Model to the object-oriented paradigm.

The explicit public interface makes the actors more clear and concise, lending an object-oriented design paradigm to the Actor Model, as opposed to an event-driven design paradigm. So, if you have existing Plain Old Java Object (POJO) code or are writing an object-oriented application, typed actors allow you to integrate the Actor Model within the existing object-oriented paradigm.

For converting the POJO bean objects into asynchronous actors that process method calls, or writing strict contract-based, object-oriented applications, typed actors can be used. Typed actors are on the cusp where the Actor Model meets the POJO world...