Configuration for redundancy?

[prev] [thread] [next] [Date index for 2005/04/05]

Greetings,

We have developed a web application using mod_perl and MySQL. We chose the 
light Apache + mod_perl Apache + MySQL method.

What we would like to be able to do is come up with a fully redundant setup of 
machines so that we can sell this package to company's, install it in their 
datacenter and thats it. 

We are not very hardware minded, so we are looking for suggestions on what 
kind of setup we should deploy. We want to keep redundancy and scalability as 
top priority.

One of our basic ideas was to have a setup of 6 machines and a raid array. 3 
machines would act as the primary machines, the remaining 3 would be backup 
machines. That would leave us with a primary and backup light Apache, same 
with mod_perl same with MySQL.

We would like to separate these three entity's so that as the install gets 
larger and larger, all we need to do is add machines for that specific 
purpose and not have to re-arrange anything.

The machines would each have a small harddrive connected to them, which will 
contain the operating system. We would then have a raid setup which the 
individual machines would mount (via NFS?) the raid setup would contain the 
database files, the core code that powers the application, and any web files 
to be served.

Like I said, we are not big into hardware, and this may be overkill or totally 
wrong. 

Any suggestions are highly appreciated!!