Re:Microservices – Not a free lunch
by muffs on Sunday December 28, 2014 @09:45AM
(#8806343)
Can you elaborate on your latter point? Why is that considered an incorrect architectural decision?
[ Parent
| on HN ]
Re:Microservices – Not a free lunch
by marktangotango on Sunday December 28, 2014 @11:06AM
(#8806525)
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.