Timeline for Message queuing systems: sequential processing with dependencies between queues
Current License: CC BY-SA 4.0
Post Revisions
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 18, 2022 at 21:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 19, 2022 at 20:06 | answer | added | Hans-Martin Mosner | timeline score: 0 | |
| S Jul 19, 2022 at 15:31 | history | suggested | davidbak | CC BY-SA 4.0 |
Changed title and added `message-queue` tag because question is more general than rabbitmq. IMO
|
| Jul 16, 2022 at 16:39 | comment | added | Alex Brohshtut | Then store the message at the init level and make pricing service produce message when it is finished to another queue, which is listened by init service | |
| Jul 16, 2022 at 15:47 | comment | added | beater | If I understand, that would require pricing service to know about invoice service and require the message originally sent pricing service to contain extra processing data to instruct it to next send a message to invoice or not. That's not acceptable. | |
| Jul 16, 2022 at 14:07 | comment | added | Alex Brohshtut | Let's say you have init service, pricing service and invoice service. Init service decides whether the current order can be processed simultaneously or invoice after pricing. If it can be done simultaneously - it sends 2 messages to queue - invoice and pricing. If the order needs to be processed in a sequence, then init service sends pricing message to queue, and the pricing service, which processed the message - sends another message (invoice) to the queue. | |
| Jul 16, 2022 at 13:07 | comment | added | beater | @AlexBrohshtut yes one possible solution is to have the application send the price message and wait for pricing completion but how to accomplish even this? | |
| Jul 16, 2022 at 8:47 | comment | added | Alex Brohshtut | I highly doubt this is possible to do in the message queue itself. You need logic to determine what type of request it is, and then if this request needs to wait for the pricing, it needs to stay somewhere. I'd implement this logic in an application and not the message broker. | |
| Jul 14, 2022 at 20:05 | comment | added | davidbak | Good question that I'd like to see an answer to - in the hopes of getting an answer I submitted an edit to widen the scope from rabbitmq only to message queuing systems in general (as IMO this is more a matter of the architecture of a message-queuing application and any proper answer would apply to (nearly) all message queueing systems, modulo details). | |
| Jul 14, 2022 at 20:03 | review | Suggested edits | |||
| S Jul 19, 2022 at 15:31 | |||||
| Jul 14, 2022 at 16:27 | review | Close votes | |||
| Jul 29, 2022 at 3:10 | |||||
| S Jul 14, 2022 at 15:48 | review | First questions | |||
| Jul 28, 2022 at 15:50 | |||||
| S Jul 14, 2022 at 15:48 | history | asked | beater | CC BY-SA 4.0 |