Infrastructure Design suggestions for a Multi-Server Aplication
Greetings
My company is working on developing a could-based business management solution.
Our developers have asked for suggestions on the best way to implement a multi-server infrastructure.
Instead of simply running a website, or server application on one box, it would need to run on many different servers to handle the processing power / db queries performed by many users.
For example, Everyone goes to Facebook.com, yet there isnt one central box that handles it the entire site.
Could someone roughly explain the theory behind how such sites like Facebook operate?
My ROUGH idea is something like this...
1. Go to Facebook.com
2. Script determines which geographical location you're in
3. You're routed to the closest NLB in the FB network.
4. you're then routed to the server inside the network which has the least number of users on it.
Please note that i only use Facebook as an example.
My company is working on developing a could-based business management solution.
Our developers have asked for suggestions on the best way to implement a multi-server infrastructure.
Instead of simply running a website, or server application on one box, it would need to run on many different servers to handle the processing power / db queries performed by many users.
For example, Everyone goes to Facebook.com, yet there isnt one central box that handles it the entire site.
Could someone roughly explain the theory behind how such sites like Facebook operate?
My ROUGH idea is something like this...
1. Go to Facebook.com
2. Script determines which geographical location you're in
3. You're routed to the closest NLB in the FB network.
4. you're then routed to the server inside the network which has the least number of users on it.
Please note that i only use Facebook as an example.
Wilder_Admin
The point is that you create one entry box in a cluster. But you will cut out the calculations process in a cloud like eucalyptus for linux. Its like in the old days when you rented cpu time in a data center. So the design of the databse is the thing you have to do first. By a small system you can log which part of your database is accessed by clients. and this part you generate new as a single database and replement the datas back in a link for your applications.
ASKER
I think what you're suggesting is that we have a different box for each part of the database.
This isn't ideal for this project as we need everything stored in one place. Users must be able to access all data their entitled to regardless of which box they're on.
Go to FB.com, chances are you're not routed to server 32 on Rack B twice... Each time it's a different box handeling your session however you can still access all the information you're meant to.
This isn't ideal for this project as we need everything stored in one place. Users must be able to access all data their entitled to regardless of which box they're on.
Go to FB.com, chances are you're not routed to server 32 on Rack B twice... Each time it's a different box handeling your session however you can still access all the information you're meant to.
The point is that the users are all on the same box but your databases not. So the routing problem is not a problem at all see here: http://open.eucalyptus.com/learn/what-is-eucalyptus
ASKER
Are you sating that a massive website like FB has "ONE" server which all users use?
Like one physical box?
How is that possible?
Like one physical box?
How is that possible?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wow,dpearson!
I sincerely appreciate your advice on this. Thank you for taking the time to write such an extensive response. I will forward this to my developers and see what they say.
In the mean time i'd like to leave this thread open and see if i can get any more ideas.
Thank you very much once again.
I sincerely appreciate your advice on this. Thank you for taking the time to write such an extensive response. I will forward this to my developers and see what they say.
In the mean time i'd like to leave this thread open and see if i can get any more ideas.
Thank you very much once again.
You're very welcome. All the best in learning about this fascinating world.
Doug
Doug
ASKER
Thank you for the help!!!