>Decoupling components >This way, the producer doesn’t need to know anything about the consumer and vice versa. Both components needs to agree on shared data,

>Decoupling components >This way, the producer doesn’t need to know anything about the consumer and vice versa. Both components needs to agree on shared data, down to what each field actually means. The producer is just not saying What To Do with the message. Take an example of processing a purchase order in multiple, asynchronous steps. While the webpage button spins there's a whole dance of agreed messages and expected outcomes that needs to happen in order for it to work. And there is no decoupling in sight. My take is that Decoupling is a vague word. One should design distributed systems assuming that coupling is manageable, not inexistent. >you could submit the task and ACK immediately allowing the job to finish in the background. That's bad practice.