2 ms·
The point here seems to essentially be "we have no standardisation" and therefore there's no point doing HATEOAS. Surely it's just a catch 22? We need more HAT
by danpalmer 12y ago
The point here seems to essentially be "we have no standardisation" and therefore there's no point doing HATEOAS.
Surely it's just a catch 22? We need more HATEOAS (because almost no one is doing it right now) before we will get the standardisation, and we need the standardisation before anyone will see the advantages clearly enough to invest time in HATEOAS.
I think the best approach is to build up the tooling for HATEOAS, get all those 'RESTful web frameworks' providing support for it, and using it within individual services to enable more fluid APIs. By this I mean APIs that can be changed to some degree to iterate, add features, or react to heavy loads on particular endpoints, while clients don't need to change each time, and can instead adapt automatically to different data being returned.
Google already do this with their private APIs for mobile applications, and that's where I think we will see growth of features that make sense to implement now.