HATEOAS (Hypermedia as the engine of application state) is an essential but often overlooked / ignored constraint of the REST architectural style. Its importance is not that significant if you’re going to define some APIs for one-time use, i.e., the benefits will only gradually reveal over time. So I draft a simple case study of a sample online order management service to show why adopting HATEOAS is so important for minimizing maintenance cost and ensure backward compatibility.
Jun
8
2009
Great presentation, very simple for people less fluent in HTTP and the Web. I’ve been using Jim Webber’s “HATEOAS: The Confusing Bit from REST” as a reference whenever people asked me about HATEOAS but now I’ll start with yours.