At work we built a microservice-like (more like meso services) architecture which uses RabbitMQ for messaging. RabbitMQ itself is great, but there are some dow

At work we built a microservice-like (more like meso services) architecture which uses RabbitMQ for messaging. RabbitMQ itself is great, but there are some downsides to this architecture: * Lots of tooling (for blue/green deployments, load balancing, autoscaling, service meshes etc.) assumes HTTP(s)+JSON or GRPC these days * Getting people who aren't deep into software engineering to write a service that connects to RabbitMQ has a much higher perceived hurdle than making them write a HTTP service * Operations is different than with HTTP-based services, and many operators aren't used to it TL;DR: it's more of a niche product for inter-service communication, which comes with all of the problems that niche products typically face.