Subscribers in Akkatecture come in the form of DomainEventSubscriber. They allow you to have listeners within the actor system listening to domain events that get published from the aggregate roots. The events that this type of subscriber listens to come from's EventStream.

//subscriber counts how many games have ended
public class GamesEndedSubscriber : DomainEventSubscriber,
ISubscribeTo<GameAggregate, GameAggregateId, GameEndedEvent>
public int Count { get; set;} = 0;
public bool Handle(IDomainEvent<GameAggregate, GameAggregateId, GameEndedEvent> domainEvent)
Logger.Info($"{Count} Games ended so far.");
return true;

DomainEventSubscribers are actors that subscribe to domain events, domain even subscribers can be thought of as tiny microservices that live within your actor system. some examples of common usages for DomainEventSubscribers could be:

  • Persist projected data.
  • Re-publish events onto external message queues.
  • Fascilitate in distributed computations and workflows.

Do take note! If your subscription actor is doing "dangerous" work, such as doing I/O, consider applying the error kernel pattern to defer the danger of I/O failure away from the subscription actor. Create a child actor that will be responsible for doing the dangerous I/O work, and then make that child actor susceptible to failure. Always defer potential exceptions away from parent actors, and let's supervision protect your domain event subscribers from failure.

If you want a subscriber to interact between aggregate or domain boundaries, Akkatecture ships with an AggregateSaga<,,> implementation that has been specifically tailored for this use case. To learn more about sagas (otherwise known as process managers, or activities, go here)

Next, Scheduled Jobs →