top | item 8806343

(no title)

muffs | 11 years ago

Can you elaborate on your latter point? Why is that considered an incorrect architectural decision?

discuss

order

marktangotango|11 years ago

For example if the caller needs the result of a possible long running task, ie success or fail, then it has to maintain state in a way to associate the async queue message back to the task. Zeromq has the concept of request/reply to handle this, its more problematic with plain old queues, the solution ive worked with is mq for tasks, rest calls for results. Yes it sucks.

muffs|11 years ago

Awesome, thanks for the explanation.