One application per server???

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

This may be off topic and, if so, I apologize, but I have a confusing
training issue to address. If anyone knows a more appropriate place to post
this question I will be glad to do so.

Can someone explain why so many business applications suggest they be
installed on their own server? I know the common reason given is that it
makes them more stable, but why?

We are installing a records management package that will use six
inter-related servers. If one of them crashes the others might as well,
because the system will still be down. Why does it matter if the database
(for instance) is on a separate server from the application server or the
content index server or (whatever)? And why should an Accounting software app
need a separate server from a Legal Dept. software program?

On home PC’s we can run multiple operating systems. So why is that any
different than running multiple applications on the same server?

I have Googled for this information with no luck and will greatly appreciate
any help!
 
Greatoutdoors said:
This may be off topic and, if so, I apologize, but I have a
confusing training issue to address. If anyone knows a more
appropriate place to post this question I will be glad to do so.

Can someone explain why so many business applications suggest they
be installed on their own server? I know the common reason given is
that it makes them more stable, but why?

We are installing a records management package that will use six
inter-related servers. If one of them crashes the others might as
well, because the system will still be down. Why does it matter if
the database (for instance) is on a separate server from the
application server or the content index server or (whatever)? And
why should an Accounting software app need a separate server from a
Legal Dept. software program?

On home PC's we can run multiple operating systems. So why is that
any different than running multiple applications on the same server?

I have Googled for this information with no luck and will greatly
appreciate any help!
Click to expand...

Don't over-think.

Best Practice vs Realistic Expectations and Possibilities.

Think of it in this simplistic way: Eliminate the Single Point of Failure.

Just because something is best practice doesn't mean it is the only way to
do things. It may be the safest, fastest, etc - but it is not the only way.
What the "best practices" almost always push - eliminate a single point of
failure. Don't put all your eggs in one basket. etc.
 
Don't believe it's stability - more reliability. It's more efficient to have
the workload spread out between different units. It's why Exchange
Server or Small Business Server is usually a separate physical box
from say the Domain Controller. Many applications require extensive
disk access, so you wouldn't want multi-tasking to delay transactions.
Server hardware isn't nearly as expensive as just a few years ago.
I'm sure one of the regular responders who architect Server configs
will post with more specific reasons.
 
Back
Top