Ask questions and see you at January, 10th, 8.PM. CET: youtube.com/c/bienadam
Also checkout recent episode:
Please keep the questions Jakarta EE-stic. Means: as short and as concise as only possible. Feel free to ask several, shorter questions. Upcoming airhacks.tv events are also going to be announced at meetup.com/airhacks
Hey Adam,
We have an interesting use case that might be a good fit for Message Queues,
An application needs to call around 5-7 operations(web hooks) per event on some write to the database, these writes could be around 2000 per hour and we need to individually retry the web hooks if they fail. Do you think that it is overkill to use a message queue? Would you recommend setting it up (the queue) ourselves or use some hosted solution?
We are using Aws for most of our hosting.
What we don't need is persistence (hence not Kafka) but reliable messages that we can after a successful external call we can say (OK this one is processed) however since this is not the core application but some external services that if are failing should not interfere with the actual code hence I was thinking no simple query for the list of hooks and call them.
Also did you recently use JMS? Do you know any recent changes?
Thanks in advance,
Guru