Discussion Locked

What is the Best Hardware Configuration

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Friends,

We are planning to setup webservers,Mailservers,database servers,Firewalls.

The webserver is going to be used for B2C transactions.We are expecting 500 hits per day intially.

1. What is the best hardware configuration for this??(IBM/HP/DELL..etc)

2.What kind of load balancing to be used??
(When we get unexpected Hits..)

3.What kind of Firwalls(Software/Hardware) to be used??

4.what's your option in Database/Webserver/Transaction processing/Secured Servers?

Thank you..

5 replies

by mckaytech

As you'll discover from the answer that follows, I'm a big fan of Linux and think you can do just about everything you need to do with it. But the choice between Microsoft, Linux, FreeBSD or Solaris is more about religion and/or cost than performance.

Hardware: Web server appliances with a personal preference for Compaq and Cobalt, but HP Netserver and IBM Netfinity are also good, solid products

Load balancing: Cisco Local Director ideally; Windows2000 Load Balancing is not a bad option in a MS environment; round-robin DNS also works.

Firewall: Cisco Pix if you can afford it; IPCHAINS on Linux appliance otherwise

Server software: Preferred - Apache/PHP running against MySQL. RedHat Professional Acceptable - IIS with ASP/SQL Server. Bulletproof - Apache on Solaris with Oracle backend.

And don't forget the power protection and backup!!!!!

paul

by dlw6

PMWRIGHT has some great suggestions, but there's no *best* answer.

It all depends on the top 2 layers of the OSI model, Money and Politics. What can you afford? Do you prefer 'NIX (better performance but harder to use) or WinXX (easier to use but inferior performance)?

As for Money, buy what you can afford. I suggest that maintenance is of equal importance to initial cost. If you plan to fix the stuff yourself, figure in a supply of spare parts for the cost. If you go with a name-brand server farm, figure in a maintenance contract. Factor in the money you might lose any time a server is down to get a feel for the importance that maintenance plays in the cost equation.

As for politics, most of us go with either (1) our childhood, which is UNIX for most of us, or (2) what everyone else is doing, which is WinXX. It depends on where your skills lie as far as which way to go.

Once you've solved those two questions, the rest is easy.

1. As much hardware as you can afford.

2. I'm not an expert on this, but the Cisco web site has some good info.

3. Checkpoint, if you can afford it. I also tried Raptor on an NT box, and I don't recommend it.

4. Get good servers, and stay on top of Service Packs. If you can afford it, put an ISS RealSecure network detector (www.iss.net) where it can protect your network from attack, perferably watching your DMZ in stealth mode. If your firewall is Checkpoint, Realsecure can reconfigure the FW on the fly. The attacker's first probe is killed by RealSecure, and by the time he realizes it failed, the FW has locked him out too.

Good fortune,
Don

This discussion is closed to new replies.