EAI Patterns with Actor Model: Routing Slip

Use a Routing Slip when a large business procedure logically does one thing but physically requires a series of processing steps. This achieves a service composition commonly recognized as SOA. In our Routing Slip process, each step is handled by an individual Actor. The process of this example is customer registration, as described by [Hohpe & Woolf], which includes the following steps:

  • Create a new customer
  • Record the customer’s contact information
  • Request a service plan for the customer
  • Run a credit check for the new customer

First let’s look at the top of RoutingSlip.scala and the Value Objects that comprise the data body of the registration message:

. . .

The full text is now available as part of my book Reactive Enterprise with Actor Model on Safari Books Online.

More to explore

Reactive DDD: Modeling Uncertainty

Domain-Driven Design supports reactive architecture and programming. Still, reactive introduces uncertainty. Back in 2003, the way that Domain-Driven Design was used and

Scroll to Top