Webhook vs queue for updates notifications
asp.net
I have an entity I am responsible for and there is a requirement to let other apps in the organization know whenever an update occurred.
It is required that each update is delivered to the other apps even if they are offline currently (no message drop tolerance).
The amount of apps is around 6 and the frequency of updates is around 50 to 100 updates a day (totally).
Each app should be able to listen to specific entities updates that are relevant to it.
One option is using a queue (say rabbit) and publish an update message that anyone can listen to.
Another option is using a webhook so each app can subscribe to changes on specific entities.
What's the preferred solution or are there other ways this should be done? Is there a best practice here?
It is required that each update is delivered to the other apps even if they are offline currently (no message drop tolerance).
The amount of apps is around 6 and the frequency of updates is around 50 to 100 updates a day (totally).
Each app should be able to listen to specific entities updates that are relevant to it.
One option is using a queue (say rabbit) and publish an update message that anyone can listen to.
Another option is using a webhook so each app can subscribe to changes on specific entities.
What's the preferred solution or are there other ways this should be done? Is there a best practice here?
