Skip to content
stateless.co · Engineering notes from the request/response layer
statelessThe engineering desk

A publication about the machinery under everyday software: the contracts between services, the queries behind a page, and the failures that only show up in production.

ArchiveAbout

About Stateless

Stateless is an engineering publication. We write about the layer most software sits on and few people describe well: what a service promises across an API, what a database does with a query that looks harmless, and what a cache returns while it is refreshing.

What we publish

One kind of article, in six sections. Each piece takes a question engineers actually ask — usually one that currently returns a scattering of forum threads and vendor documentation — and answers it completely: the mechanism, the trade-offs, the edge cases, and the point at which the usual advice stops working.

We do not run news, launch coverage, funding rounds or opinion about the industry. If a piece cannot tell you what to do differently on Monday, it does not run.

The domain

stateless.co has carried writing about hypermedia and HTTP since 2011. The original HAL specification — the media type behind application/hal+json — was published at this address, and the posts that argued it into existence are still here, in the archive. Nothing has been deleted: the addresses are cited from standards discussions and reading lists, and breaking them would be vandalism.

Those archive pages are marked as archive material. They record what this domain published at the time; they are not current guidance from the present publication.

Independence

Stateless is an independent publication and is not connected with, and does not speak for, any consultancy or company that has previously operated under this name. Any similarity of naming follows from the history of the domain.

Money

The publication carries paid placements. They are labelled, they carry rel="sponsored", and they never buy a position inside an editorial piece. Details are on the placements page.

How we work

Sourcing, corrections and what we do when we get something wrong — the working method.