blog
Honest writing about what Rindle is, how it's built, and where its edges are — for people deciding whether to build on it.
The HTTP surfaces around Rindle's WebSocket data plane: how the api-server turns a named query into a lease, how writes stay exactly-once, and how errors tell you what to do.
read →How a browser finds its read follower and stays there: the write-master / read-follower split, the signed affinity ticket, and what happens when a follower dies or lags.
read →An honest account of Rindle Cloud — the problems it's shaped for, the ones it isn't, and where the edges are. Written for someone deciding whether to build on it, not to sell them on it.
read →