4 ms·
> I'm a huge advocate of log based architectures, which take message passing architectures to another level. That is, message passing architectures are good at
by kitd 11y ago
> I'm a huge advocate of log based architectures, which take message passing architectures to another level. That is, message passing architectures are good at limiting the things that can happen, log based architectures do that and add the benefit of capturing what did happen.
AKA Event-based programming. Events are what has happened. Components define what events to respond to and how.
In practice you need a combination of events and messages (or 'commands'). Which one to use depends on NFRs like dependency, complexity, performance, maintainability, etc.
- kasey_junk 11y agoI don't know if there is a formal taxonomy of these things, but I tend break down messaging passing architectures along the what/how axes. So you can have events or commands being sent in your messaging based architecture as the what. Log based architectures really speak to the how. That is, the medium for message exchange is a durable log. But like you said, in the real world they tend to be hybrids across all these lines.