Password storage is one of the few areas in software with a genuine right answer, published, maintained and free. It is also one of the most consistently got wrong, because the wrong answers were correct at some point and nobody revisited them. The failure is rarely exotic. It is a system built in 2016 against advice...
Backend Development
Articles, guides and tutorials on backend development, covering server-side languages, databases, APIs and architecture for scalable applications.
Technical documentation fails in a specific and predictable way. Somebody writes a great deal of it during a quiet fortnight, the system changes, nobody updates it, and within a year the document is confidently wrong. At that point it is worse than nothing, because a reader who trusts it acts on information that no...
An uptime SLA looks like a promise and behaves like a refund policy. Suppliers know this. Customers frequently do not, and sign a service level agreement believing they have bought availability when what they have bought is a small discount in the event they do not get it. That is not necessarily a bad deal. It is a...
Disaster recovery in a small team is usually one line in a document nobody has opened: backups are enabled. That statement is true and it is not an answer, because it says nothing about how old the data would be, how long the restore takes, or whether anyone has ever performed one. The gap between having backups and...
API versioning arguments usually start at the wrong end, with where the version number goes. That is the least consequential decision in the whole subject. What matters is which changes require a new version at all, and most teams get that wrong in the direction of complacency: they ship something they believe is...
Database performance work usually begins with someone proposing a bigger instance, and it usually ends with the discovery that one query was doing a sequential scan over four million rows on every page load. The hardware was never the constraint. The plan was. That pattern is consistent enough to be worth stating as a...
Cloudflare Queues solves the problem every serverless application eventually hits: a request arrives that triggers work the user should not have to wait for. Sending the confirmation email, resizing the upload, syncing the record to a third party. On a traditional server you hand that to a background worker process. On...
Cloudflare Hyperdrive exists because of a specific, unglamorous problem: a Worker running in two hundred cities talking to one Postgres database in one city is slower than the same query issued from a single server sitting next to that database. Not slightly slower. Often several times slower, and for reasons that have...
Cloudflare Workers and AWS Lambda are both serverless compute platforms, but they come from different starting points. Lambda is the established serverless standard inside the vast AWS ecosystem; Workers is edge-native, built for low latency and global distribution. In 2026, both are excellent, and the right choice...
Cloudflare Workers let you run backend code at the edge, close to your users, without managing servers. For APIs, that combination of near-zero cold starts, global distribution, and tightly integrated storage makes Workers a compelling platform in 2026. This guide explains how a Cloudflare Workers API is structured and...