Consul in practice
2018.253Service discovery, health checks, and dynamic config across a growing fleet of microservices -- and the moment KV store got too popular.
architecture
all tags →Service discovery, health checks, and dynamic config across a growing fleet of microservices -- and the moment KV store got too popular.
A GraphQL gateway that started as a unified API layer for clients became the place where we could intervene without touching the backends.
I've built a rules engine twice, in two languages, at two scales. The tree is the same.
What a digital wallet looks like underneath -- a balance, a ledger, idempotency keys, and the gap between moving money and moving money correctly.
A rules engine that answers yes or no during checkout, with condition trees built by people who don't code.
Picking the first piece to cut from a Perl monolith, rewriting it in Go, and switching over before you lose your nerve.
What a codebase looks like when two people build everything -- 350 commits, and a todo list with two items.
Adding businesses to a social platform built on Neo4j -- and realizing both sides of the marketplace use the same graph patterns.
Two people, one Express app, and eight middleware functions between the request and the response.
Replacing an e-commerce frontend without turning off the old one -- carving over layer by layer while the store takes orders.