How often is Spring HATEOAS used in real projects?

Question

Java

When studying spring, I began to consider the Spring HATEOAS module and, in general, the HATEOAS approach. It feels more complex and confusing than with fixed query interfaces. How often is this module (approach) used and for what tasks is it better to use it?

Answer 1

So you go to the Toaster, create questions, browse, the site is updated, new features appear, but have you ever had to update your client (browser) in order to use new features?
I didn't have to, I just needed to refresh the page, and get updated hypertext with new possibilities for state transitions.
Here you have HATEOAS, used often. Profit - extensibility, scalability without the need to update the client.
Thanks to HATEOAS in particular, we see the Web as it is today and at its current scale.
And if you add unique urls, self-descriptive messages, caching, do not store the client state on the server, use media types known to the client and server, you can get the REST API (there are more nuances)