d-engine Dev Notes (Part 1): The Hard Parts of Software Development
Why I started d-engine, and three lessons from building it: wanting has a cost, follow the flow, and make complexity visible.
Read the article →Raft consensus, embedded coordination, and the engineering behind d-engine and the projects built on it.
Why I started d-engine, and three lessons from building it: wanting has a cost, follow the flow, and make complexity visible.
Read the article →d-lmdb-server is now available as a Docker image — spin up a 3-node HA cluster and see leader failover in action in about 5 minutes.
Exploring how to add replication to an embedded KV (LMDB) using d-engine, with minimal changes to the read path.
A practical look at what d-engine gives you as a developer — embedding, deployment patterns, and the architecture decisions behind it — with links to the examples so you can try it yourself.
I built d-engine because distributed coordination should be accessible — cheap to run, simple to use, and honest about its trade-offs. This post explains why, and what I'm building.