Should you design APIs based on what you (the owning team) think is the best way to expose your domain, or do you make compromises based on the needs of your API's consumers?
(API here refers to any element of the public contract of your service/subsystem/app/domain/context, such as HTTP endpoints or events.)
You start from any conventions you've agreed on with other teams regarding API design.
Then you focus on what's best for your domain model.
And when you find reality has needs beyond what both convention and model dictate, you inspect and adapt. That means revisiting a convention or remodeling your domain boundary.
Add comment