3 ms·
There's a lot of good reasons why you shouldn't just connect straight to the database from client-side code. [1] So you'll always need some form of server sitti
by mmillin 6y ago
There's a lot of good reasons why you shouldn't just connect straight to the database from client-side code. [1] So you'll always need some form of server sitting in between. Maybe you could store it in a new database system built entirely for this, which handles all of the nuances. However, you nearly always have more complicated logic and constraints that need to be enforced beyond what can be specified in a database schema, and you can't rely on clients maintaining that.
[1]: https://security.stackexchange.com/q/229954 https://security.stackexchange.com/q/229954
- devxpy 6y agoI agree that direct connection to a database might not be the best idea, but I dont see anything particularly wrong with sending SQL over the wire. I'm suggesting something like a hassura that isn't based on graphql, but works directly on SQL. And ofcourse for specific logic, you can always run a traditional server in tandem.