The Immutable Architecture of Event Sourcing

Event sourcing is this at least piecewise linear set of events, a historical model. So the picklist and the invoice are both historical facts. They're happened. There's their decisions that somebody made based on that order. The transaction has already been received but asynchronously now distributes it to various sources that care for it. That's computation. That's machine show. You can solve that. But I mean, this is where you get into that sort of relationship mapping thing. It says, this is what the incoming stream looks like. Maybe it's blobs. It doesn't really matter. Whatever it comes to you. And it maps it out asynchronously.