'How to prevent loops with an event driven architecture
In our organization, we are implementing the API LED Connectivity pattern together with an event driven architecture. We basically want source systems to publish events on which subscribers can react to do something, mostly updating their own source system. There is one major issue with our design on which we currently have no solution. So we'd like to ask for your help!
Our problem is that events will trigger an update loop. Below picture describes in an extremely simplified way what we want, and what will happen:
An update in System A, will update System B, which will create an event and update System A, which will create an event and update System B etc. etc.
How can we stop this loop, considering the following:
We cannot prevent System B from sending events. Due to the complexity of many source systems, we have no influence on this. So System B will send events We cannot ignore events of System B to System A, because there could be data in that event that really needs to be updated in System A Any help is appreciated, thanks!
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|