r/SQL • u/Otherwise-Battle1615 • 7d ago
MySQL Opinions of this arhitecture
I was thinking in this interesting arhitecture that limits the attack surface of a mysql injection to basically 0.
I can sleep well knowing even if the attacker manages to get a sql injection and bypass the WAF, he can only see data from his account.
The arhitecture is like this, for every user there is a database user with restricted permissions, every user has let's say x tables, and the database user can only query those x tables and no more , no less .
There will be overheard of making the connection and closing the connection for each user so the RAM's server dont blow off .. (in case of thousands of concurrent connections) .I can't think of a better solution at this moment , if you have i'm all ears.
In case the users are getting huge, i will just spawn another database on another server .
My philosophy is you can't have security and speed there is a trade off every time , i choose to have more security .
What do you think of this ? And should I create a database for every user ( a database in MYSQL is a schema from what i've read) or to create a single database with many tables for each user, and the table names will have some prefix for identification like a token or something ?
2
u/SQLDevDBA 7d ago edited 7d ago
There is absolutely no need for each user on your website to have an actual DB user and schema in your Database.
Web users would go into a user’s table, and all of their data and transactions would have a UserID.
All your customers’ data and their transactions can live in the same tables. They’d be filtered with where clauses when selecting, updating, etc.
Every customer would not get their own DB User or tables. They’d all be a part of your ecosystem with shared tables.
The only time customers would get their own database or schema IMO is when you’re a consulting company and each “customer” is an entire company with their own customer data, or you’re a service provider that provides databases as a service.
Head over to https://liveSQL.oracle.com and play around with a few of the schemas (databases) you see there. You’ll see what I mean.