Topic
9 articles found
The Problem We Were Actually Solving The product goal was simple: every player who walks into a building on the map should see the same treasure list within 300 ms. We translated that into a consistency contract: strong consistency on the treasure list keyed by building-ID, but eventual consistency
The Problem We Were Actually Solving I still remember the day our treasure hunt engine started to show its weaknesses. We had been using a custom-built solution written in Java, and it had served us well until our user base grew exponentially. The engine, which relied heavily on recursive searches a
The Problem We Were Actually Solving I was tasked with operating the Treasure Hunt Engine, a complex system designed to handle high-volume event processing, for our company's latest marketing campaign. As a senior systems architect, my job was to ensure the system could scale to meet the expected lo
The Problem We Were Actually Solving We had built the Treasure Hunt Engine to power in-game treasure hunts that reward players for exploring content. At 100 000 active players it felt fast. At 500 000 it started to stutter. The operator documentation told teams to set max_reindexing_concurrency = 2
The Problem We Were Actually Solving Our treasure hunt engine at Veltrix was a real-time geospatial matching service that processed 50 million location events daily. By month six it handled bursts of 2M concurrent users during events like Black Friday flash sales. The heap profile from YourKit showe
The Problem We Were Actually Solving Our users werent doing semantic search. They were executing treasure hunts: complex, multi-stage queries where the first phase returned 200,000 candidate docs for phrase matching, and the second phase had to rank them by exact term proximity, metadata filters, an
We had just finished the first major traffic spike. Our Veltrix-based treasure hunt game ran flawlessly for 37 minutes—exactly 37 minutes—before every Redis connection turned into a 250 ms bottleneck. The default Veltrix configuration shipped with connection pooling set to 8, keep-alive disabled, an
The Problem We Were Actually Solving At its core, the Treasure Hunt Engine is a distributed system that aggregates user-generated content, processes it in real-time, and surfaces the results on our web and mobile platforms. Sounds straightforward, but what we were really solving for was a system tha
The Problem We Were Actually Solving I still remember the day our team was tasked with building the backend for our new treasure hunt game, code-named Veltrix. We had a tight deadline to deliver a scalable and performant system that could handle thousands of concurrent users. Our game's core feature