3 ms·
I both agree and disagree... in the case of software, in general you usually want two boundaries, regardless of if you are the only one generating them... betwe
by tracker1 11y ago
I both agree and disagree... in the case of software, in general you usually want two boundaries, regardless of if you are the only one generating them... between your front end and your data... usually front to back, and back to database.
This is part of the reason I don't instantly like solutions that expose databases to web front ends... usually the types of permissions typically needed are made excessively hard or impossible... A resource can be owned by one person, viewed by peers, partially readable by others, and manageable by command structure (management). That's just typical.
Beyond this are the differences between users/logins and accounts... too many systems will conflate the two on the backend even though they can be presented as tethered to begin with, the backend should definitely separate the two.
Given, most APIs are political boundaries within an organization... this isn't entirely a bad things. But that is far from the only reason to create/use those boundaries... security and data integrity are two more.