In my previous post, No REST for the Wicked, I gave my two cents on REST and the underlying principle of HATEOAS (Hypermedia As The Engine Of Application State). In my opinion, HATEOAS is applicable to more than just REST architecture. The internet trolls may argue that I’m using the term too broadly, but HATEOAS introduces a number of concepts that are worth exploring in their own right.
You can hardly mention the terms API or REST without tripping over some developer’s rant about which API’s are RESTful and which are not. Frankly, I’m running out of reasons to care. Standards and paradigms are tools, not goals. So to everyone still debating over what is and isn’t RESTful I say, “Your mom’s API isn’t REStful.”