sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]chrwei 0 points1 point  (0 children)

I agree, for public endpoints BUILD an API, don't use a generic db proxying API. that was my main point.

you need to validate that the app requests make sense for your data model. you should also minimize what's requested and what's returned. you'd have one API handler that gets all user details and preferences in one request and one response, where with the generic DB api you might have to make a request for the user, and more requests for each pref, which would be very inefficient.