Customers Dont Always Connect Where They LiveCustomers Don't Always Connect Where They Live By David Leonhardt
Pop Quiz: You have an international website and you want to do business in Canada. But you want to make sure your website delivers top performance to your Canadian customers: speed, accessibility, as well as proper functioning of digital certificates, forms, password protections, shopping carts and more. In which of the following cities would want a website monitoring station?
•Toronto, Canada's metropolis •Montreal, Canada's second largest city •Vancouver, Canada's third largest city. •Ottawa, Canada's capital and fourth largest city •Calgary, Canada's fifth largest city.
|
Warning: file_get_contents(http://pipes.yahoo.com/pipes/OOZUroPD2xGqzv_EjwtvUw/run?_render=rss&textinput1=argus;auto;maroc;gratuitwebfr): failed to open stream: HTTP request failed! HTTP/1.1 999 Unable to process request at this time -- error 999
in /home/httpd/vhosts/allhostguide.com/httpdocs/includes/pipes_feed.php on line 40
| Browse Hosting Plans |
 HomePrivate/DedicatedCo-LocatedShared/VirtualUnix/LinuxWindowsBudget (<$10)FreeSearchArticlesContactPrivacy PolicyAdd to Favorites |
| Did You Know? |
Webfarms: The Only Way To Host!Networks can be configured to be so incredibly redundant now - for reasonable prices - that there is no excuse for a data center not to achieve five nines (99.999%) of availability.
But what about the servers and applications? Why spend so much time up front configuring the network to make sure it doesn't fail, and then deploy an application to a single server?
Sure, there are ways to make sure individual servers have some redundancy to minimize failures -- things like RAID1, RAID5, or RAID10 (redundant array of inexpensive disks) which will protect against a disk drive failure (and I highly recommend this type of configuration for all production servers - and preferably the use of hardware RAID vs. software RAID). But what happens if a file gets corrupt on the RAID array? Or a recent configuration change brings the application down? Or a newly released patch conflicts with other settings and causes problems? Well, in these situations the server will go down and the application(s) hosted on that server will be offline.
A good monitoring and alerting process will allow the system administrator to detect and address these issues quickly, but still there will be some level of downtime associated with the issue. And depending on the type of issue, even the best system administrator might not be able to immediately resolve the issue - it may take time. Time during which your application is unavailable and you may be losing business due to the site interruption.
|