shipped, unused

A company API rebuilt around HATEOAS

Implemented HATEOAS properly across a company's API, the way the papers describe it. Every request then spent processing time assembling the URLs and the list of actions a client could take next. The only things that ever read any of it were the company's own client libraries — written by the same team, entirely under their control — and carrying it made those libraries more complex rather than less. An interesting idea in theory. A nightmare to run.

Told by gsibble on Hacker News, 9 Jul 2025. Retold here in our words, with some of theirs kept; the original is linked above.

Written by them, summarised by us, and linked back. Ask us to take it down and we will, no questions.