How many endpoints is too many for an API?
I am creating an API which the app I am developing will utilise. This app will be like a social network, and have various sections to it (Login, Posts, Messages, Friends, etc). This is my first time developing an api to work alongside an app, so I wanted some guidance.
Is it better practice to have a controller for each of these sections (LoginController, MessageController, etc). Or am I better off making seperate APIs for each section (Login API, Messaging API). I suspect each section will contain around 10-15 endpoints.
0 comments:
Post a Comment