“API design: Why you should use links, not keys, to represent relationships in APIs” According to this post on the @google Cloud Blog, “Links are simply better”. I agree :) cloud.google.com/blog/produc…

API design: Why you should use links, not keys, to represent relationships in APIs | Google Cloud...

While links aren’t widely used in APIs, some very prominent web APIs use links based on HTTP URLs to represent relationships, which has several advantages. This post shows you why.

cloud.google.com
8
106
8
305
The server defining URLs (as opposed to the client building them) is also the core of HATEOAS. Speaking of which - it’s a bit unfortunate that the name of such a good concept starts with the word “hate”.
2
1
Replying to @suhlig @Google
That acronym is unfortunate (and not part of @fielding’s thesis). Small nitpick: It’s fine for the client to build URIs if the “recipe” for doing so is sent by the server in response to a preceding request (as done with HTML GET forms)

May 12, 2019 · 9:52 AM UTC

2
2
Replying to @stilkov @suhlig @Google @fielding
And OpenSearch description documents!
1
Replying to @stilkov @suhlig @Google
Afaik @fielding does not like that acronym either and uses the term „hypermedia constraint“ instead