We turned off Pub/Sub and nobody noticed
Our entire event-driven platform ran through a single message broker, which made it a single point of failure. So we added a second one. This is the story of building an event load balancer, the queueing theory behind it, and the chaos test where we turned off Pub/Sub in production and nobody noticed.
Summary
Learn how a company improved its event-driven architecture by implementing a second message broker, conducting a chaos test, and successfully turning off their main Pub/Sub service without any disruption. The insights gained from this experience highlight the importance of redundancy and load balancing in system design.
Comments (6 of ) ⌛