In Vaughn Vernon's Red Book (Implementing DDD) he talks about storing domain events in the same transaction as the one which updates an aggregate, and then out of band you read this domain event store (not in the event sourcing sense) in order to put messages on a message queue, for example, to notify remote bounded contexts.
In an akka-cassandra-kafka world, with no transactions, I imagine an actor with an akka persistence query stream, that is responsible for putting a domain event on a Kafka topic. In this scenario, would errors writing to the Kafka topic be handled with retries and ultimately human intervention? Is the way to add retry semantics to stream computation to send the stream contents to an actor ref which does the writing? In short: are there any good examples yet of the akka persistence approach to DDD, including published domain events (which I think are distinct from raw persistence events). -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
