https://localhost:1313/Recent content in Home on AssembluHugo -- gohugo.ioeninfo@assemb.lu (Assemblu)info@assemb.lu (Assemblu)© 2025 AssembluMon, 27 Oct 2025 14:38:44 +0100https://localhost:1313/posts/thread-safe-hyperliquid-ingestion-real-time-freshness/Mon, 27 Oct 2025 14:38:44 +0100info@assemb.lu (Assemblu)https://localhost:1313/posts/thread-safe-hyperliquid-ingestion-real-time-freshness/<p>Shipping market data out of Hyperliquid looks simple until the pipes clog. My ingestion service was running inside a single container with three moving parts: a WebSocket listener, a PostgreSQL batch writer, and a NATS publisher. The new monitoring thread I introduced last week caught stalled pipelines in minutes, but it also uncovered a couple of subtle threading bugs and a nasty freshness regression. This post walks through what went wrong, how I fixed it in C++, and why the service now holds a rock-solid one second stale-data delta.</p>