It's an interesting question. I am working on an application that (if it works out for the client) may grow to support thousands of users with requirements for high availability.
If it ever grows that far, then I expect that we will need to redevelop at least some parts of the application .
For me, the first step (to a small cluster) would be to hive off the database onto a cluster of three to five servers. DB access on this system is heavy, so that will be the likely first bottleneck.
After that, I am not sure. I think that I would likely just replicate the entire application across multiple web servers, and hand out the requests in a round robin to the web servers.
I would be very interested to hear anyone else's thoughts on this too. Does the development team have any recommendations about the best approach to scaling up a site?
Regards, Langdon keymaster wrote:
.. just dreaming, but.. If one wanted to use cake to build an app which is scalable to the extreme, ie. flickr.com or yourtube.com or myspace.com, how would you do it? Would you just separate out the db server and replicate the rest on identical nodes in a cluster? Would you break up the app into view servers, controller servers, and model servers? Imagine you were tasked with building one of these systems, what system architecture would you have?
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
