Why separate application server from database??? WHY???

[DWW]

Why do people separate application servers directly from database systems... even though they have to buy two servers.

What is the rational behind this????

If failure rate of quality components is say 0.27% chance a year per machine (made up figure for home made server... 1 day out of a year pretend for something very active and x86) then you increase your chances for more downtime if you introduce a whole other server into the equation to 2 days out of a year (or whatever expected downtime is...)

I never understood it. Especially if the application requires low CPU usage, but puts through tons of database inserts and selects.

 

[kag]

cuz the seller wants to make more money?

 

[Rogue]

It's usually part of a careful planning process that includes future possibilities too. Just because that database is small now, doesn't mean it won't become unweildy and large in the future. Just because that application server isn't doing much server side processing doesn't mean that future revisions won't do that. It's really about overhead and future proofing. Plus, you have to consider other things too, such as backup routines, security (that's a big one right there) and numerous other issues.

 

[her209]

You can distribute the database over several computers.