AMAmr Mubarakinamr-mubarak.hashnode.dev·Aug 13 · 19 min readDistributed KV Store Part 4Every part so far has had the same asterisk on GET: it only reads the local node. Part 3 made writes genuinely distributed — a value written through any node ends up on multiple replicas — but a read 00
AMAmr Mubarakinamr-mubarak.hashnode.dev·Aug 12 · 22 min readDistributed KV Store Part 3Part 2 gave every node a way to compute a key's replica set independently. Nothing used that computation yet — a PUT still only ever touched the local node it landed on. This part makes that computati00
AMAmr Mubarakinamr-mubarak.hashnode.dev·Aug 11 · 16 min readDistributed KV Store Part 2Part 1 built one node: an HTTP server with an in-memory store behind it. This part turns that single process into a member of a cluster. By the end, three separate node processes will each be able to 00
AMAmr Mubarakinamr-mubarak.hashnode.dev·Aug 11 · 14 min readDistributed KV Store Part 1 This is the first part of a series that builds a Dynamo-style distributed key-value store in Go. The finished system will partition keys across nodes with consistent hashing, replicate each key to mul00
AMAmr Mubarakinamr-mubarak.hashnode.dev·Aug 11 · 18 min readFrom PostgreSQL WAL to SearchLogical Replication, Publications, Slots, and LSNs Applications end up needing the same thing over and over: some other system has to find out when a row changes. A search index needs to know when an 00
