SCSam Critchleyinauthagonal.hashnode.dev·1d ago · 4 min readYour backup quietly resurrects the users you deletedEvery incremental backup makes the same quiet assumption: to back up what changed, find the rows that changed. On a key-value store like Azure Table Storage or DynamoDB, "what changed" means "rows who00
SCSam Critchleyinauthagonal.hashnode.dev·3d ago · 6 min readWe run a whole auth system on stores that only know get and putAn auth system looks like it wants a relational database. Users, roles, sessions, OAuth grants, refresh tokens, all cross-referenced. Ours does not use one. It runs on Azure Table Storage, a store tha00
SCSam Critchleyinauthagonal.hashnode.dev·6d ago · 6 min readOne hyphen, two tenants, one signing keyTwo of our tenants were the same tenant. They had different names, different signups, and different billing rows. They also shared a database and a token-signing key, and none of the three of us, the 00
SCSam Critchleyinauthagonal.hashnode.dev·Jul 6 · 4 min readScale-to-zero can't count to oneThe advice always had the same shape. Your auth traffic is spiky. Your Kubernetes cluster sits mostly quiet. Azure Container Apps scales to zero and bills you for what you use. You are paying around t00
SCSam Critchleyinauthagonal.hashnode.dev·Jul 3 · 4 min readLeaving self-hosted Duende: what migrates, and what you stop operatingDuende IdentityServer is a genuinely good piece of software — if you want to own your identity layer end to end, it's the standard in .NET. But "owning it" is the whole cost: you host it, patch it, sc00
