3 ms·
I thought REST didn't define much so basically every API can be REST conform. Just because HATEOAS makes REST APIs better, doesn't mean those without the use
by k__ 10y ago
I thought REST didn't define much so basically every API can be REST conform.
Just because HATEOAS makes REST APIs better, doesn't mean those without the use of it aren't REST.
Even SOAP can be REST conform.
Anyway, I guess with the rise of GraphQL, which is more strict (at least in its definition) REST will go away and we will have better dev life's.
- icebraining 10y agoI thought REST didn't define much It does, it's just at a different level. REST is not a protocol, it's a set of architectural constraints, but it's well defined. Only one of the constraints (code-on-demand) is optional. HATEOAS isn't, since you need it to achieve the Uniform Interface that allows you to decouple the clients from the services.