EAI Patterns with Actor Model: Recipient List

We’ve looked at a few different kinds of Content-Based Routers, and Recipient List is yet another. A Recipient List is compared to the To: and Cc: fields in an email message, where you specify any number of intended recipients of the email message. Thus, a Recipient List may be predetermined depending on the kind of message being sent. Yet, it is also possible for a Recipient List to take on the characteristics of a Dynamic Router in that the recipients may be determined by some set of business rules.

The example provided here performs price quoting. When the MountaineeringSuppliesOrderProcessor receives a RequestForQuotation message, it calculates a Recipient List based on a set of business rules, which means it is a kind of Dynamic Router.

. . .

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