The Problem We Were Actually Solving I was tasked with designing and implementing a scalable event handling mechanism for our company's treasure hunt engine, a system that would be used by thousands of users simultaneously. The system had to be able to handle a high volume of events, such as user movements, treasure discoveries, and leaderboard updates, while ensuring low latency and high throughput. As I delved deeper into the problem, I realized that the event handling mechanism was not just about processing events, but also about ensuring data consistency, handling failures, and providing a good user experience. Our initial prototype was built using a popular message broker, but we soon realized that it was not designed to handle the complexity of our use case. The broker was causing significant latency, and our system was unable to handle the high volume of events.…