Looking Data Base for page and gameserver
- Thread starter fa1thDEV
- Start date
What specific queries are we talking about?
The build very rarely interrupts the database.
Create simple protection for connecting to the database.
And a backup
And what's the point of moving the database outside the localhost?
In my region, the community is very malicious and looks for anything to cause trouble. My idea was that, for example, everything related to rankings and visuals that requires queries should be done on a database external to the main one. This way, the server would continue to function normally with its queries, and the website with the UCP would function normally with its database, because they usually send bots or spam queries. But I just thought that I could update the ranking every hour using cache, so that nothing breaksWhat specific queries are we talking about?
The build very rarely interrupts the database.
Create simple protection for connecting to the database.
And a backup
And what's the point of moving the database outside the localhost?
I say "two" DB in one vps, one for main server and the other for the host/page/cp, what do you think?
Maybe I misunderstood you, but keeping the server database, website database, and server on the same machine is not the best idea.
I say this:
A database for the page (mirror database) for data, i.e. rankings, information systems, raid bosses, how many are online, so that if they hit you with update times
So when it comes to donations or services, that's when it interacts with the MAIN DB, but it would be protecting the main DB from overloads in the event of an attack or heavy traffic. I've seen large-scale games do this, but since I've never had Lucera online, I don't know how the query and network system works
Initially, this is, of course, a site with a database injection.
Basic protection involves creating separate users for each request.
You don't need just one user.
If this is for registration and inventory items, create a database user who can only create accounts and view inventory.
Also, create a separate user for the donation system.
If your site receives a dedicated IP, you can name it usernameDB@IP.
The rest depends on the site (its settings and vulnerabilities).
If you correctly grant permissions to new database users, you're already 80% successful
Furthermore, you can control IPs using various methods, such as IPtables, Fail2Ban, and so on...
I did exactly what you are thinking about:
ServerA - main game server
ServerB - vps with website
On ServerA in mysql I created a user that would be allowed only from ServerB's IP - this user can only READ data.
On ServerB I created a python script that connects to ServerA database and reads all the needed info and saves it locally on ServerB. Website uses information from local ServerB database.
Setup cron for python script to run each X minutes/hours and you are good to go, website rankings no longer need direct connection to your main DB.
ServerA - main game server
ServerB - vps with website
On ServerA in mysql I created a user that would be allowed only from ServerB's IP - this user can only READ data.
On ServerB I created a python script that connects to ServerA database and reads all the needed info and saves it locally on ServerB. Website uses information from local ServerB database.
Setup cron for python script to run each X minutes/hours and you are good to go, website rankings no longer need direct connection to your main DB.