EVENT SOURCING — THE PRIVILEGED MODEL FOR INDIRECTION — PART 3

• You can read the part 1 here.
• You can read the part 2 here.

In the last parts it was presented an evolutionary path towards an event driven architecture to support multiple read models. We ended with an architecture with a relational database that supports write operations where the business invariants are ensured, an event queue, a broker to dispatch messages, and an Integrator to update changes to read-only databases (Image 1). In this part 3 It will be presented an Event Sourcing alternative and…