Building Real-Time Trading Systems: Why We Abandoned Go for Rust
The microsecond-level performance data that forced our complete architectural rewrite Building Real-Time Trading Systems: Why We Abandon
Curated development tutorials from top sources. Filter by language.
The microsecond-level performance data that forced our complete architectural rewrite Building Real-Time Trading Systems: Why We Abandon
Yesterday I shipped 1.9.0. Got a solid mix of hate and genuinely useful feedback. Didn't sleep. Took all of it personally. Built 2.0.0 instead. No po
I have been working on a realtime multiplayer server in Go. The transport layer is WebSocket using gorilla/websocket, and most outbound payloads are
This is the story of why I rebuilt google-researcher-mcp (Node.js/TypeScript) from scratch as web-researcher-mcp (Go), and what the lessons learned al
4 hours of sleep a night for the past few days. ForgeZero went from 1.0 to 1.9.0 in that time. This isn't work anymore. This is obsession. Let me
So I've been solo-building fz — a fast, opinionated build tool for C/ASM projects written in Go. No Makefile hell, no CMake nightmares. Just a single
I wanted to practice Go regularly by building real projects, so I decided to solve a problem I personally face: expense tracking. For the last few mo
Let me tell you a story that starts in 2013, peaks somewhere around 2019, and ends with me staring at a $4,200 AWS bill at 11pm on a Tuesday.
Backstory: A year ago I built a speech-to-text assistant for myself, because on Linux this has always been a pain and there still was not r
TL;DR NornicDB's MVCC layer assigns each committed write a (CommitTimestamp, CommitSequence) pair, where CommitTimestamp comes from time.No
How embedding schema versions in every data file — observations, controls, output, baselines — enables forward compatibility, fail-fast loading, and c
In the previous article we defined the Canary CRD. Now we build the Operator: the controller that watches Canary resources and drives the actual relea
In the previous seven articles we've thoroughly explored the Informer framework — Reflector, DeltaFIFO, Indexer, WorkQueue, EventBroadcaster, and the
Over the past six articles we've examined each component of the Informer framework individually. Now it's time to look at the component that wires the
In the previous article we covered WorkQueue — the retry and rate-limiting backbone of controllers. In this article we look at a different but equally
In the previous article we saw how Indexer stores and indexes resource objects for fast local queries. Now we look at the other half of the controller
In the previous article we saw that HandleDeltas routes every event to two destinations — one of them is Indexer. Indexer is the local in-memory cache
In the previous article we saw how Reflector calls List/Watch and feeds events downstream. The immediate destination of those events is DeltaFIFO — th
In the previous article we saw that Informer's core mechanism is List/Watch. The component responsible for executing that mechanism is Reflector. Ever
If you've ever built a Kubernetes controller — or wondered how kube-controller-manager keeps thousands of resources in sync — the answer is Informer.