excerpt from the dbslayer website http://code.nytimes.com/projects/dbslayer
"The typical LAMP strategy for scaling up data-driven applications is to replicate slave databases to every web server, but this approach can hit scaling limitations for high-volume websites, where processes can overwhelm their given backend DB's connection limits. Quite frankly, we wanted to scale the front-end webservers and backend database servers separately without having to coordinate them. " best regards On Wed, Oct 14, 2009 at 9:32 AM, Atif Ghaffar <[email protected]>wrote: > Stefan, > yes. to control resource usage on the db server and to calculate when > scaling the db is needed. > Exactly the same reason what dbslayer was intended for : Separating the > scaling of the db from the scaling of everything else. > > > > > On Wed, Oct 14, 2009 at 9:27 AM, Stefan de Konink <[email protected]>wrote: > >> On Wed, 14 Oct 2009, Atif Ghaffar wrote: >> >> > There is no _pre_ about what we are doing, we are in >> > post-post-post-almost-dead-beaten-horse state :-) >> >> So to resume; the only thing you want this for is administrative reasons? >> >> >> Stefan >> >> > > > -- > best regards > Atif Ghaffar > -- best regards Atif Ghaffar
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
