Concept for async event handling

This page describes the concept for asynchronous event processing in our web application.

For simplification reasons we used synchronous event processing so far. But as described on this page the usage of asynchronous event processing is mandatory for being able to replay axon events at some time. So we need to have a look at how this could work, because Oregami will fundamentally rely on review principles for gathered information from users.

Articles about the problem:

4 Ways to Handle Eventual Consistency on the UI

Stackoverflow: Showing changes in View when using CQRS & DDD with Domain Events & ServiceBus

Google Groups: how to get client UI updates from read model in a CQRS+ES system

Busting some CQRS myths

PDF: An In-Depth Look at Event Sourcing with CQRS