- [Instructor] One goal in microservice architectures
is to avoid tight coupling.
It's hard to uncouple rickvest that are needed
to show data on the website instantly
but when it comes to posting data to a service,
doing that asynchronously through some intermediate service
removes any dependency between color and receiving service.
Queues are a common way to accomplish that
and the basic principle is very simple.
Basically they provide a way to publish messages to it.
So if we have here the conference app
and the feedback service
and we put a queue in between we can now
publish those feedback messages to the queue
and they will then show up on the queue.
And there can be several messages
so everything will end up on the queue.
When the feedback service is available
it can then call consume on this queue.
And after it consume the message it can acknowledge
that it received it successfully.
In this case this message will then
be removed from the queue.
There are several queuing systems available
and if you are on a infrastructure provider
like AWS Azure or Google Cloud they will come out of the box
In this course we will be using RabbitMQ to publish
and consume feedback messages asynchronously.
RabbitMQ is available for all common operating systems
and has a client library for notches.
As such it's a good candidate for showing
the basic functionality of queues in this course.
In the next video, I will cover how to set it up.