|
|
Posted by Gleep on 09/08/07 19:34
Hope someone can provide some insight.
I'm doing some googling but not finding what I need.
I'm planning on putting together an application that will allow users to
upload many multi media files. But lets say my current provider limits
me to 300 gigs of HD space. I fully expect to fill that up, then I
would need to get another server and then another and so on.
So for example on server1 I would have 0-5000 members, server2 would
have 5001-10000 members and so on. I was thinking that the main
database would be on primary server and that there would be field that
contains what server the user is assigned to. So when I go to that user
(from a search or directly) the url is adjusted and the visitor is
redirected to correct server.
I don't know if this is the right approach or not. The thing is, if I
redirect a user to another server, I would no longer have the same db
connection, so if a visitor did another query, would I redirect back to
primary server run the query and be redirected back to assigned server?
Or would it be best to set up duplicated databases with master/slave
script. I was thinking one way to trick this out is to use a frame, or
a frame div with ajax. So I maintain a constant db connection on
primary server yet the data/files are pathed from whatever server they
are assigned to. I have no idea how those large server cluster farms
work, it just seems logical to me right now from what I know.
It's all sort of confusing, not sure how to approach this. Also I'm
looking at the term load balancing it seems as if the multiple servers
are exact duplicates of each other and visitors are just redirected to
particular server. In my case I would need to divide up my users to
various servers because is space considerations.
Can anyone sort of push me in the right direction to figure this out.
Thanks.
Navigation:
[Reply to this message]
|