4 ms·
This is an API guideline, not a strict REST one. Also it has become very clear to me everyone has a different interpretation of what REST can or should be. We a
by BigChiefSmokem 10y ago
This is an API guideline, not a strict REST one. Also it has become very clear to me everyone has a different interpretation of what REST can or should be. We all are quick to forget that the actual acronym stands for "representational state transfer" which is an abstract concept and therefore can be implemented in many, many different ways.
- deleted 10y ago[deleted]
- daliwali 10y ago>it has become very clear to me everyone has a different interpretation of what REST can or should be This is very true, the term has been abused so much that it has no relation to its original meaning. We can loosely define REST by one of its key qualities: hypermedia, that is a lot easier to say than HATEOAS. By focusing on this distinction, it rules out 99% of APIs in the wild. On top of that, hypermedia media types and linked data are important for an API to be self-documenting, so there is a rather high bar for developers to implement.
- deleted 10y ago[deleted]
- edblarney 10y agoIt's heavy 'REST' oriented. A Java guideline for API's would like completely different.
- cdcarter 10y agoThe guide actually explicitly says it is focused on gRPC.