4 ms·
Yes. The decision calculus here really boils down to how many clients the API has and how much you care about those clients. If you have 100 other teams each w
by throwawaygh 6y ago
Yes. The decision calculus here really boils down to how many clients the API has and how much you care about those clients.
If you have 100 other teams each with 5+ developers consuming your API -- or especially if your API is a product -- then keeping the API to frontend interface relatively stable with rare breaking changes is much more valuable than saving yourself even a major time commitment on DB to API work.
On the other hand, if you have relatively few clients -- or if the clients are "lower status"/"cheaper" teams -- saving time on the DB to API work a the expense of client teams might make sense.