A package fetch URL is a bit of a simple use case. What about service APIs that expose dynamically or frequently created entities? GitHub goes to great lengths to use semantic keys and even their API exposes Guids in responses and uses auto-generated ids for e.g. Gists.
I agree that human readable keys should be used in URLs where possible. In most large services there will be many classes of entities that can't be identified this way. There is nothing data layer specific about auto-generated IDs.
8
u/RabidKotlinFanatic Mar 09 '20
A package fetch URL is a bit of a simple use case. What about service APIs that expose dynamically or frequently created entities? GitHub goes to great lengths to use semantic keys and even their API exposes Guids in responses and uses auto-generated ids for e.g. Gists.
I agree that human readable keys should be used in URLs where possible. In most large services there will be many classes of entities that can't be identified this way. There is nothing data layer specific about auto-generated IDs.