Use links not keys to represent relationships in APIs

Re:Use links not keys to represent relationships in APIs by smadge on Sunday May 12, 2019 @05:31AM (#19890963)

I don’t think we should follow a 2 decade old thesis dogmatically, but I would point out that Roy Fielding has said:

“A REST API should be entered with no prior knowledge beyond the initial URI (bookmark) and set of standardized media types“

In this case the only URL that is support long term is the entry point into the application. All other resources are discoverable from the index.

[ Parent | on HN ]

Re:Use links not keys to represent relationships in APIs by bartread on Sunday May 12, 2019 @05:47AM (#19891005)

This really is an old quote, and some people certainly do cling to it quite dogmatically, but my own experience suggests that slavishly following this principle makes life more difficult for both producers and consumers, and that there's little substitute for excellent API documentation, and clear, timely communication of changes.

[ Parent | on HN ]

Re:Use links not keys to represent relationships in APIs by mpnally on Monday May 13, 2019 @11:16AM (#19900100)

I don't think Fielding meant to say that you cannot bookmark a URL, which is what your interpretation would imply. He was only commenting on how you find the URL in the first place to bookmark it.

[ Parent | on HN ]

Re:Use links not keys to represent relationships in APIs by imtringued on Monday May 13, 2019 @06:23AM (#19897772)

REST isn't SOAP. What you're describing just adds unnecessary complexity.

[ Parent | on HN ]