News for hackers. Stuff that matters.

A comment on Use links not keys to represent relationships in APIs. Parent comment

Re:Use links not keys to represent relationships in APIs by jeltz on Sunday May 12, 2019 @09:29AM (#19891759)
What determined which API owns a resource when the same resource is exposed in mutlipe apis (e.g you have a REST API and a AMQP feed)? In some cases it is obvious but in other cases it is far from clear.

I feel using urls as ids create more problems than it solves, especially if you use absolute urls. I have worked with cases where the same ID was used in 3 or 4 different APIs. None of them clearly the master.

[ Parent | on HN ]
Re:Use links not keys to represent relationships in APIs by tuukkah on Sunday May 12, 2019 @02:19PM (#19893514)
The URI doesn't have to be fully owned by any single microservice. The JSON representation can more or less correspond to a HTML view and be served by the UI, or a separate API facade can combine the relevant pieces of information from various microservices.
[ Parent | on HN ]