Why we urgently need offline cloud computing redundancy in Kenya

Recently the East African undersea cables SEACOM and TEAMS experienced a major Internet outage when the cable they connect to, the SEA-ME-WE 4 cable, was damaged on the Mediterranean sea bed.

As Moses Kemibaro explains, the outage was a shock to those now used to speedy Internet access and he calls for cloud computing redundancy:

The outage required Internet Service Providers (ISPs) and Telcos to re-route their bandwidth via expensive satellite connections so as to maintain some semblance of connectivity – this tended from very bad to quite slow depending on your choice of service provider. It is for this very reason why we urgently need to have local clouds that function even when international bandwidth and cloud are not available. This way, essential cloud-based services will continue to function locally.

I'd like to take his idea one step father - we need offline cloud computing redundancy, not just local-to-Kenya redundancy. While I can appreciate that Nairobi Internet users would want to still reach servers in Westlands if SEACOm or TEAMS were down, those in Kisumu or Eldoret want their cloud services if the link to Nairobi goes down. And as well Kakamega or Siaya if their links to larger cities go down.

So this means re-thinking cloud computing from a central server farm in the USA or even in Nairobi, to many smaller server gardens in many local locations. Redundancy that can ensure connectivity to your apps, no matter which link goes down. A redundancy kinda like the Internet itself.

That's why I say that with cloud computing, all weather is local.

Like this? Then friend us on Facebook

Wayan Vota's picture

Wayan Vota

Inveneo

Wayan Vota is a technology expert focused on appropriate information and communication technologies (ICT) for rural and underserved areas of the developing world. He is a Senior Director at Inveneo and is the editor of ICTworks

Cloud Computing Fault Tolerance/Redundancy in Kenya

Moses, I think proper Cloud Infrastructure Design should in the minimum be comprised of infrastructure spread out across multiple availability zones such that in the event of a failure, business critical application will still be available and there would be no interruption of service.

e.g. An e-commerce website consisting of 20 Load balanced web,search, and backed database servers should be spread in at least two availability zones such that e.g. if the infra in the Nairobi Datacenter goes offline for power or whatever reason, traffic is routed to the other set of 10 servers in the Kisumu Datacenter.

Edwin.

Amazon Cloud - Multiple Availability Zones going down.

In reference to the above, Amazon EC2 US East region went down last week due to a poorly executed switch upgrade.

Its is advisable to spread Application servers and database servers in different regions. Amazon reported multiple availablity zones in the same region going down ,customers who did not have their services spread in multiple regions experienced service disruption.

http://www.networkworld.com/news/2011/042111-amazon-ec2-zones.html?ap1=rcb

Edwin.

Why we urgently need offline

Reading along, i am totally agreeable to the idea that cloud structuring design should at least be comprising of infrastructure spread all over vast availability areas so that in the event of failure, applications should still be available and not hamper the on-going services.