Personal experience: I needed a message broker while working with multiple sensors constantly streaming data at high frequency. I have seen a startup where Rab

Personal experience: I needed a message broker while working with multiple sensors constantly streaming data at high frequency. I have seen a startup where RabbitMQ was being used to hand-off requests to APIs (services) that take long to respond. I argued for unifying queueing and data persistence technology using Postgres even though I know a simple webhook would suffice. Given that AWS has to sell and complexity tends to make people look smart, another server was spurn up for RabbitMQ :) Many companies that have run a highly distributed system have figured what works for them. If requests are within the read and write rates of what Redis or Postgres can handle why introduce RabbitMQ or Kafka :? Always remember that the Engineer nudging you towards more complexity will not be there when the chips are down.