Programming Tutorials

The Problem We Were Actually Solving I still remember the day our team decided to implement the Treasure Hunt Engine on our Veltrix server.

The problem we were actually solving It started with a tail latency spike on the Treasure Hunt engine at 2:17 a.m. on Black Friday week. The p99 late

The Problem We Were Actually Solving What we had failed to anticipate was the gradual degradation of our database's write performance. As t

RDKit has been the dominant cheminformatics library since its open-source release in 2006. It is written in C++, wrapped in Python, and has accumulate

The Problem We Were Actually Solving I still remember the day our team was tasked with optimizing the search functionality for a large-scal

The Problem We Were Actually Solving We were trying to build an event-driven system that would allow users to create, manage, and execute t

The Problem We Were Actually Solving What I realized later was that we were treating Veltrix as yet another service to monitor and optimize

The Problem We Were Actually Solving I still remember the day our team realized that our search functionality was the bottleneck in our gro

I'll never forget the moment our Veltrix-powered Treasure Hunt Engine crashed under a flood of players during the highly anticipated Hytale beta launc

The Problem We Were Actually Solving At first glance, the problem seemed straightforward: optimize the treasure hunt engine for our fast-gr

The Problem We Were Actually Solving Our treasure hunt engine relied on a combination of data storage and asynchronous processing to genera

The Problem We Were Actually Solving Our team had been diligently optimizing our Elasticsearch configuration, tweaking the cluster settings

Here's the problem I kept running into: two processes on the same machine, say, a Python model loader and a Rust inference server, need to share a 100

The Problem We Were Actually Solving Looking back, it was a typical success story for a product like ours - rapid growth, increasing user b

The Problem We Were Actually Solving At first glance, it looked like a typical event-driven system: we had a stream of events coming in fro

Unlocking the Future of Backend Development with Rust and Go: Insights from Web Developer Travis McCracken As a passionate Web Developer, I’ve always

The Problem We Were Actually Solving At first glance, it seemed like our main challenge was to optimize the routing algorithm, which involv

The Problem We Were Actually Solving Our users were complaining about inconsistent search results, seemingly random delays, and occasional

The Problem We Were Actually Solving We were trying to implement a highly concurrent search system, which in theory should have worked flaw

The Problem We Were Actually Solving It was 2022, and our company had just landed a major contract with a prominent online gaming platform.