Hello,

I have a client that will soon outgrow their existing single-server
environment. Their current setup is a mixture of HTML,Perl & PHP scripts,
the latter two connect to a MySQL backend.

I'm curious how others have handled this problem. As a first line of
defence, we plan on splitting the web server from the MySQL server. After
that, we'll need to load balance.

How are have others handled this situation? Is anyone using MySQL clusters?
What do you use for the Apache load balancing (yes we use sessions)? Any
tips, references, warnings you'd like to suggest would be appreciated.

Thanks,
Kevin

On Tue, 15 Mar 2005 13:15:29 -0500, in
comp.infosystems.www.servers.unix, "Kevin" <kevin@wxREMOVE4SPAM3.com>
wrote:

>Hello,
>
>I have a client that will soon outgrow their existing single-server
>environment. Their current setup is a mixture of HTML,Perl & PHP scripts,
>the latter two connect to a MySQL backend.
>
>I'm curious how others have handled this problem. As a first line of
>defence, we plan on splitting the web server from the MySQL server. After
>that, we'll need to load balance.
>
>How are have others handled this situation? Is anyone using MySQL clusters?
>What do you use for the Apache load balancing (yes we use sessions)? Any
>tips, references, warnings you'd like to suggest would be appreciated.
>

Not sure how much of this applies, but...

We went through several steps

1) add a server and split the web traffic by assigning different IP
address to the virtual hosts.

2) multiple web servers behind a load balancer. Initially had the
load balancer forwarding based on number of connections but have
switched to round-robin due to issues with hanging FTP connections
that all go to one server. No more web servers run on the database
system. The application is stateless - any on-going info is in
.

HTH,
Jim

Kevin wrote:

> I'm curious how others have handled this problem.

Use what you have efficiently. If you're using old-fashioned
technology like CGI or LAMP, upgrade your software infrastructure!

See http://www.apachetutor.org/dev/reslist for a discussion of the
subject. The principles - a far more scalable architecture than
CGI or LAMP - still hold, although the software referenced in the
article was rendered obsolete by the integration of native SQL
support[1] in APR/Apache.

[1] the MySQL driver is separate due to licensing issues: it's GPL and
so can't be distributed from apache.org. But once you've downloaded it,
it's as simple as building "--with-mysql".

--
Nick Kew