ICTworks by Inveneo

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

This Saturday, March 27th, the Nairobi Google Tools User Group is meeting at Nairobi Institute of Technology from 10:30am – 1:00pm.

The Nairobi GTUG holds regular meetings to keep you updated on Google technologies and how potential they can be for your Internet enabled application or even enterprise.

During the meetups, GTUG members share resources, skills & knowledge about Google technology & services, spreading dirty little tricks about Google's technologies, or simply chat with each other talking about all of Google's tools.

To stay updated, please join the mailing list at: http://groups.google.com/group/nairobigtug/

.

Recently there's been a good discussion about cloud computing in Africa, where Ken Banks asks if its "Inappropriate" appropriate technology? Ken starts by suggesting that:

If we take anything that uses “the cloud“, for example, then I’d argue that it’s largely “inappropriate” unless you’re working in predominantly urban areas or in predominantly ‘developed’ countries.

7.47 Kbps download speed in Nigeria

Why? Well cloud computing relies on realtime server interactions with low latency, high bandwidth, and a stable connection. None of those are common in most of Africa. As an example, 193 Kbps in Ghana is the best bandwidth speed I've found in my Africa travels. Or as Miguel says:

The Cloud is predicated on having an "always on" connection to function. While it's fine to design a web architecture that centrally stores user data and handles all the heavy lifting when it comes to processing, the issue of access is going to block off Africa and whole lot of the rest of the world because of this. Designers (if they can be nudged to care) need to build applications with this in mind for probably the next 5-10 years. It's building in "graceful degradation" to a system.

But why live in the now? Others look to a brighter, more connected future with announcements like 3.5G in rural Ghana. Specifically, Matt Berg makes the point that we should not close our minds to the rapid growth of bandwidth options that make cloud computing possible:

The data quality of GSM networks in places like Africa is improving dramatically and will soon offer (if they don’t already) performance comparable to the West. Assuming the well funded operators can weather the growing pains of widespread data adoption, I think we can expect the quality and reliability to improve. Also in terms of GSM networks rural areas will increasingly = urban areas as operators extend services.

In addition, the quick spread of technology infrastructure can reduce some of the connectivity constraints that Miguel described. Alice Liu points out that much of the long distances data must now cover to reach American or European server farms is shortening as infrastructure moves onto the continent:

The cloud doesn’t necessarily mean connecting back to California as another person mentioned. MTN in Kigali, for instance, offers data center/hosting services and many governments are setting up their own data centers and IT service centers to serve other government units. I’m hoping this takes off, because in govt they’re all competing for the same scarce IT resources.

But I think the best point in the whole discussion is made by Michael Downey, when he says that, like politics or the weather, all technology is local:

“Appropriate” technology is based 100% on context of who users are and the environments in which they will work and live. Thus, there’s a danger of over-generalizing any technology, such as emerging platforms like cloud computing, and even more proven platforms such as mobile devices.

Choosing the right solution for a given situation is what's paramount, not any one specific technology. In high-bandwidth areas where users have devices that can browse the Internet quickly and cheaply, cloud computing can make great sense. I used my mobile phone web browser more in Accra, Ghana than the USA. Yet in Nigeria, Internet bandwidth is so poor and unreliable, VoIP intranets beat Skype for voice communications and cloud computing would be a joke.

So its best not to watch international news for the right technology solutions to implement in your specific project. Like the weather, its best to be local and look out the window to see what's appropriate for your day - be it cloudy or not.