Many hosting companies have based their Windows®-based Hosting environments on the concept of shared application pooling. By sharing AppPools, those companies achieved server densities similar to those seen on Apache (Linux/Unix). But for any customer with a Website that processes credit card information directly, or has proprietary scripts, this is a significant problem.
Sharing AppPools in a Windows-based hosting environment is the quickest and easiest way to get started with an offering based on Windows. It’s easy to implement, and it provides for maximum server density. Maximum server density usually means maximum profit. Unfortunately, this method also means that the server is inherently less secure — the more accounts in an AppPool, the more things that can go wrong or cause the sites within that AppPool to crash, and therefore the more customers who will be affected by such a calamity.
Verio Hosting for Windows accounts, built around individual AppPools, essentially isolate customer sites — which by definition makes them secure. This is very important given that Microsoft® software and applications are the most widely adopted in the world; therefore they are attacked by hackers more often.
| Type: | Whitepaper |
| Posted: | May 29, 2007 |
| Format: | |
| Length: | 5 pages |
| Language: | English |
| Topic: | Information Management |
| Email this Page |
|
| Print this Page |
|
|
|
|
| Find Related Reports | |
