Re:Use links not keys to represent relationships in APIs
by treve on Sunday May 12, 2019 @02:33PM
(#19893602)
Just a thought:
If in your example your usergroup and user are managed by the same service, then usually you should already have a feature in your framework that parses `/user/123` into its individual component and finds the relevant entity.
If in your example your usergroup and user are managed by the same service, then usually you should already have a feature in your framework that parses `/user/123` into its individual component and finds the relevant entity.
Ideally you would use that.