All shared web hosting, reseller hosting (which is the same), and VPS hosting , is based on stacking loads and loads of websites on a single physical server.
Server’s have become more and more reliable over the years, and it’s common for them to run more than a few years without crashing.
If a single server breaks, and your sites are on there, or your customers sites, its a world of pain. They all have spare and redundant hardware in that server, to make it as reliable as possible. But eventually the inevitable happens.
With a clustered solution, your site is duplicated to several different servers. wpdone distributes your sites to 3 different servers, in 3 different data centres. We might suffer the same hardware crash, but we’ll just turn off the effected server, and run your sites from a working server. We can then recover the server in peace.
When one of these servers has a hardware crash, or has a software problem, or is hacked – the results can be dramatic. And there is a knock on effect, and generally it is 4-10 days to recover, and this is why:
So the outcome is
The next thing is I am not ‘bashing’ other providers. It’s not naming and shaming, but without concrete real examples, it’s difficult to believe.
A few weeks ago, netvirtue here in Australia has some big problems on a single server, but the customers on there were upset:
From the thread, you can see it went on for days, perhaps a week for some accounts. source :http://forums.whirlpool.net.au/archive/2495421
And the big outage of the week was Heart internet in the UK. These guys are down for 4 days, and counting. Again, some customer it will be a week of outages. Check out the guy in the youtube below, he is the best testamount of why single server hosting is bad.
The biggest difference in clustered hosting is how recoveries of disasters happen.
Single server hosting, the recovery is slow, lots of support tickets, and it takes multiple days. There is a lot of sweat, swearing, customer calls, and long nights.
Clustered hosting recovers in a few seconds. Then we can recover the broken server in peace, without support tickets or customer calls, in business hours, without pressure, and without receiving internet web hits (which just slows everything down as well).
By Scott Farrell on February 14th, 2016