Let's assume a web app made of independent modules:example.com/accountingexample.com/employeesexample.com/adminNext step is adding an API which normally might end like this:example.com/api/v1/accountingexample.com/api/v1/employeesexample.com/api/v1/adminI worked before like this and it was the most natural thing, but now that each sub-app is a whole unique beast that even have independent deployment operations, this pattern came up as an idea:example.com/accounting/api/v1example.com/employees/api/v1example.com/admin/api/v1/Are there any downsides between both ways of organizing my API across modules that I should be aware of? I am trying to think about deployment costs, caching, security... but cannot come up with any clear disadvantage. The only thing that bothers me is my habit of having all api operations under a common root path.
API design for modular apps
api;api design