Hello Axon users,
I think that a typical problem that people have is to delete/update a bunch of aggregates when someone else does.
I have an Aggregate referred by others, and when it goes, eventually all the others must update. E.g. if I unsubscribe from facebook, all my facebook friends should lose me as a friend.
Resorting to the read layer to find those other seems quick enough, but it’s not 100% safe.
The alterative seems instead a lot harder. Maybe to keep a Saga to track the inverse references, send the update commands once there is the delete, and keep sending it for any new reference that is created after it.
There are more possibilities. Hopefully something simpler… Anyone has a take on this?