Frans van Buul another look at event-driven architecture for a perspective you might not have seen to learn about messaging patterns, coupling, and more.
Gartner has identified this as one of the top 10 technology trends for 2018. “Events” occur very naturally in many business domains, which by itself is a good reason to make them an explicit part of software systems. They can be processed asynchronously.
Two anti-patterns considered:
- Messaging pattern
- Coupling
As per messaging anti-pattern he points out that messages between systems are not just that: they may also be things like instructions to do something. To represent a command (“post a new blog entry”) like an event (“there has been a request to post this new blog entry”) is unnatural.
A command represents a desire by the sender to change or do something. It should be handled exactly once, and the sender often expects a confirmation, since a command may fail. This is a totally different case from sending an event.
Learn about coupling problems in the article. Great read!
[Read More]