Database Question

Hello, i'm working now on browser game, i'm doing scheme - how server will work for now, and i'm new in this .

I have a question, i will run two servers Login_Server and Game_Server, but i think
if online will reach 3-5k+ players it will lag, and i think, better to add one more server "Database_Server"

Login_Server -> Game_Server <--> Database_Server

Database_Server will contain all the player data,items,pets_data,guilds,legions,etc ... ( all that player gained in game )

This is good idea, or i will fail on packets x2 ?

The log in shouldn't have it's own server. The users are going to have to be logged in to play. They play on the game server, and the log in data should be stored on the database.

So you should have a DB server daemon and the game server daemon. If the load gets unbearable, you should have enough money by then to buy more server computers (which you have plenty of time before that becomes a problem- if it does). The load from your game or database can be distributed across several computers. The actual server daemons only need to be set up as services across those computers.

Having more software- such as a login server- isn't going to decrease the load.

The reason database servers are necessary is because flat-file databases are too slow. The idea of a log in isn't simplified by having it's own server.

Quote:

---

Originally Posted by s-p-n

Having more software- such as a login server- isn't going to decrease the load.

---

For the Login_Server software, the idea was to protect the Game_server stability from the broot, hacks, ddos ...

Quote:

---

Originally Posted by tanomist

For the Login_Server software, the idea was to protect the Game_server stability from the broot, hacks, ddos ...

---

How u gonna do that with a list of users and passwords? And what's stopping the hacker from hacking/brute-forcing the login-server in order to perform ddos on ur game?

If you get more than a maximum number of requests per second, ignore the requests from that IP long enough for the database to log the user out. If you want to forward the requests to a dumby server, then u don't have to rely on it to log ur users in.

If you want to implement your plan as-is, then go ahead. I only gave advice because you posted.

Quote:

---

Originally Posted by s-p-n

How u gonna do that with a list of users and passwords? And what's stopping the hacker from hacking/brute-forcing the login-server in order to perform ddos on ur game?

If you get more than a maximum number of requests per second, ignore the requests from that IP long enough for the database to log the user out. If you want to forward the requests to a dumby server, then u don't have to rely on it to log ur users in.

If you want to implement your plan as-is, then go ahead. I only gave advice because you posted.

---

Yes i agree, ignoring packets is a good one also, but while some one is pushing on login server, the game server will not be effected, also and the Database server

it will kinda like

Login_Server - Security
Game_Server - Read Only
Database_Server - Read/Write user Information

...