0

I'm building a simple API as an apprentice developer and ran into a small problem. It would make my life easier to expose some data twice, using URI's like so: api/Xs/{XId}/Ys and api/Ys/{YId}/Xs, so that aggregation can be performed by the API as opposed to by the client. In my example, X and Y have a many-to-many relationship.

Is this considered bad practice? I have tried to search for the answer, but I don't know exactly how to describe this other than 'exposing data twice'.

flumperious
  • 164
  • 1
  • 7

0 Answers0