Have you ever wanted to make a call to an external system, and receive a response with some data? If you've ever made an API call through HTTP, this is exactly what you're doing.
But what if you're not using HTTP? What if you have a system sitting on the other end of a RabbitMQ configuration, and you need to get information out of that system and back in to your application?
With the wascally library that you saw in the previous episode, this is easier done than said! Wascally bakes the idea of request/reply (aka “remote procedure call”, aka “request / response”) directly in to the API. You only need to “.reply” to a message and you now have instant access to remote procedure calls for any system that is connected to your RabbitMQ setup.
In this episode, you'll learn how to properly make request/reply calls with RabbitMQ and wascally. You'll see how Wascally sets this up, and you'll learn the core pattern behind this feature.
If you've ever wanted to make an API call without having to set up an HTTP API end-point, then you're in the right place. RabbitMQ and wascally will make this dream a reality, in less time than you can imagine.