Published On Mar 2, 2022
What's the request-response pattern for? We're used to synchronous communication. You make a request to another service and get a response. When you move to asynchronous communication, you often think of messages as fire-and-forget. You send a command to a queue, and the consumer handles it asynchronously. Because of the temporal decoupling, you don't know when the message was processed or what the result was. However, there is a solution! Let me explain how you can use the request-response pattern to reply sender once a message is processed.
đź”— EventStoreDB
https://eventsto.re/codeopinion
đź”” Subscribe:    / @codeopinion Â
đź’Ą Join this channel to get access to source code & demos!
   / @codeopinion Â
🔥 Don't have the JOIN button? Support me on Patreon!
  / codeopinion Â
đź“ť Blog: https://codeopinion.com
đź‘‹ Twitter:   / codeopinion Â
✨ LinkedIn:   / dcomartin Â
📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo...
0:00 Intro
0:45 Synchronous Request-Response
2:24 Asynchronous Request-Response
4:53 Code Example
#softwarearchitecture #eventdrivenarchitecture #messagedrivenarchitecture