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.

Vaughn Vernon

Vaughn Vernon

Vaughn Vernon is a Software Ecologist, Architect, Modeler. Vaughn is a leading expert in Domain-Driven Design, and a champion of simplicity and reactive systems. He consults and teaches around Domain-Driven Design and reactive software development, helping teams and organizations realize the potential of business-driven and reactive systems as they transition from technology-driven legacy web implementation approaches. As he does so, he puts strong emphasis on embracing simplicity whenever possible. Vaughn is the author of four books: Implementing Domain-Driven Design, Domain-Driven Design Distilled, Strategic Monoliths and Microservices, and Reactive Messaging Patterns with the Actor Model, all published by Addison-Wesley.

More to explore

Reactive DDD: Modeling Uncertainty

March 14, 2023

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