I would like to present the fruits many years’ labor trying to build a reusable set of components for building (web) applications really driven by Hypermedia.
The HATEOAS constraint boils down to a simple rule that the client cannot make assumptions about the resource representations and possible state transitions; all the necessary information should be provided by the server at run time. This poses a great obstacle when juxtaposed with the typical mindset, particularly that of designing Single-Page Applications. Single-Page Applications, or SPAs, are often built around rigid navigation structures (aka routing) and bespoke views and forms. Such approach to building software is a wasted opportunity for resilience to changes. The result is a set of bad practices such as code generation from API descriptions, and API versioning.
October 23, 2019 12:40