Messaging with Actors
For more details and full analysis of each pattern described in this section, please refer to Chapter 4 of Reactive Messaging Patterns with the Actor Model by Vaughn Vernon.
Sections
- Introduction
- Messaging with Actors
- Messaging Channels
- Message Construction
- Message Routing
- Message Transformation
- Message Endpoints
- System Management and Infrastructure
Message Channel
Connect the applications using a Message Channel, where one application writes information to the channel and the other one reads that information from the channel. When using Akka.NET, this concept is represented by the actor's mailbox.
Message
Package the information into a Message, a data record that the messaging system can transmit through a message channel. Messages are sent between actors to exchange information.
Pipes and Filters
Use the Pipes and Filters architectural style to divide a larger processing task into a sequence of smaller, independent processing steps (Filters) that are connected by channels (Pipes). This pattern allows to chain actors together while keeping them independent.
Message Router
Insert a special filter, a Message Router, which consumes a Message from one Message Channel and republishes it to a different Message Channel channel depending on a set of conditions.
Message Endpoint
Connect an application to a messaging channel using a Message Endpoint, a client of the messaging system that the application can then use to send or receive messages. When using Akka.NET they are actors.