3 ms·

Here's a really simple way to get a cycle. Service A: publish a notification indicating that some new data is available. Service B: consume these notification

Here's a really simple way to get a cycle. Service A: publish a notification indicating that some new data is available. Service B: consume these notifications and call back to service A with queries for the changed data and perhaps surrounding context. What would you recommend when something like this is desired?

9rx 10mo ago
There is no cycle here. Service B initiates the connection to Service A in order to receive notifications, and Service B initiates the connection to Service A to query for changed data. Service A never initiates a connection with Service B. If Service B went offline, Service A would never notice.
10000truths 10mo ago
That's not a cycle - service B isn't writing any new data to A.