To add to this, the fact that message queues are natively based on asynchronous protocols allow them to be more efficient and scalable. Sure you might be able to implement async patterns over HTTP, but the cost of setting creating the TCP connection and negotiating SSL/TLS for every request creates significant overhead on your system.
I also feel like the word async gets misunderstood so often because it can take on different meanings depending on the context when discussing microservices. For those who are interested, I've tried to outline some of these different meanings here.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To add to this, the fact that message queues are natively based on asynchronous protocols allow them to be more efficient and scalable. Sure you might be able to implement async patterns over HTTP, but the cost of setting creating the TCP connection and negotiating SSL/TLS for every request creates significant overhead on your system.
I also feel like the word async gets misunderstood so often because it can take on different meanings depending on the context when discussing microservices. For those who are interested, I've tried to outline some of these different meanings here.