Sunday, July 27, 2008

Cloud Availability

Cloud Computing has become very widespread with startups as well as divisions of banks, pharmaceuticals companies and other large corporations using them for computing and storage.
Amazon Web Services has led the pack with it's innovation and execution, with services such S3 storage service, EC2 compute cloud, and SimpleDB online database.

Many options exist today for cloud services, for hosting, storage and application hosting. Some examples are below:
Hosting Storage Applications
Amazon EC2 Amazon S3 opSource
MOSSO Nirvanix Google Apps
GoGrid Microsoft Mesh Salesforce.com
AppNexus EMC Mozy
Google AppEngine MOSSO CloudFS
flexiscale

[A good compilation of cloud computing is here, with a nice list of providers here. Also worth checking out is this post.]

The high availability of these cloud services becomes more important with some of these companies relying on these services for their critical infrastructure. Recent outages of Amazon S3 (here and here) have raised some important questions such as this - S3 Outage Highlights Fragility of Web Services and this.

[A simple search on search.twitter.com can tell you things that you won't find on web pages. Check it out with this search, this and this.]

There has been some discussion on the high availability of cloud services and some possible solutions. For example the following posts - "Strategy: Front S3 with a Caching Proxy" and "Responding to Amazon's S3 outage".

Here I am writing of some thoughts on how these cloud services can be made highly available, by following the traditional path of redundancy.

Cloud Availability configurations The traditional way of using AWS S3 is to use it with AWS EC2 (config #0).

Configurations such as on the left can be made to make your computing and storage not dependent on the same service provider.
Config #1, config #2 and config #3 mix and match some of the more flexible computing services with storage services.
In theory the compute and the storage can be separately replaced by a colo service.


The configurations on the right are examples of providing high availability by making a "hot-standby".

Config #4 makes the storage service hot-standby and config #5 separates the web-service layer from the application layer,
and makes the whole application+storage layer as hot-standby.

A hot-standby requires three things to be configured - rsync, monitoring and switchover.

rsync needs to be configured between hot-standby servers, to make sure that most of the application and data components
are up to date on the online-server. So for example in config #4 one has to rsync 'Amazon S3' to 'Nirvanix' - that's pretty
easy to setup. In fact, if we add more automation, we can "turn-off" a standby server after making sure that the
data-source is synced up. Though that assumes that the server provisioning time is an acceptable downtime,
i.e. the RTO (Recovery time objective) is within acceptable limits.

This also requires that you are monitoring each of the web services. One might have to do service-heartbeating -
this has to be designed for the application, this has to be designed differently for monitoring Tomcat, MySQL,
Apache or their sub-components. In theory it would be nice if a cloud computing service would export APIs,
for example an API for http://status.aws.amazon.com/ , http://status.mosso.com/ or http://heartbeat.skype.com/.
However, most of the times the status page is updated much later after the service goes down. So, that wouldn't help much.
Switchover from the online-server/service to the hot-standby would probably have to be done by hand.
This requires a handshake with the upper layer so that requests stop and start going to the new service
when you trigger the switchover. This might become interesting with stateful-services and also where
you cannot drop any packets, so quiscing may have to be done for the requests before the switchover takes place.


Above are two configurations of multi-tiered web-services, where each service is built on a different cloud service. This is a theoretical configuration, since I don't know of many good cloud services, there are only a few. But this may represent a possible future, where the space
becomes fragmented, with many service providers.

Config #7 is config #6 with hot-standby for each of the service layers.
Again this is a theoretical configuration.

Cost Impact
Any of the hot-standby configurations would have cost impact - adding any extra layer of high-availability immediately adds to the cost, at least doubling the cost of the infrastructure. This cost increase can be reduced by making only those parts of your infrastructure highly-available that affect your business the most. It depends on how much business impact does a downtime cause, and therefore how much money can be spent on the infrastructure.

One of the ways to make the configurations more cost effective is to make them active-active configuration also called a load balanced configuration - these configurations would make use of all the allocated resources and would send traffic to both the servers. This configuration is much more difficult to design - for example if you put the hot-standby-storage in active-active configuration then every "write" (DB insert) must go to both the storage-servers, writes (DB insert) must not complete on any replicas (also called mirrored write consistency).

Cloud Computing becoming mainstream
As cloud computing becomes more mainstream - larger web companies may start using these services, they may put a part of their infrastructure on a compute cloud. For example, I can imagine a cloud dedicated for "data mining" being used by several companies, these may have servers with large HDDs and memory and may specialize in cluster software such as Hadoop.

Lastly I would like to cover my favorite topic -why would I still use services that cost more for my core services instead of using cloud computing?
  1. The most important reason would be 24x7 support. Hosting providers such as servepath and rackspace provide support. When I give a call to the support at 2PM India time, they have a support guy picking up my calls – that’s a great thing. Believe me 24x7 support is a very difficult thing to do.
  2. These hosting providers give me more configurability for RAM/disk/CPU
  3. I can have more control over the network and storage topology of my infrastructure
  4. Point #2 above can give me consistent throughput and latency for I/O access, and network access
  5. These services give me better SLAs
  6. Security

Labels: , , , , , ,

15 Comments:

Blogger Anup Tapadia said...

Nice thoughts Mukul !!!
The colo service seems to be an outsider solution to the problem. There might be tons of compatibility challenges to build cross platform services.
VMWARE and XEN have been working extensively on building redundant Virtual Machines for failover management. If the cloud hosting providers enable these kind of features, it would be possible to have an exact replica of our current VM instance with complete state sync running on different physical machines or on completely co-located clouds. With this service providers will be able to comply to SLA's and all of this will be transparent to the cloud user. More thoughts?

12:30 PM  
Anonymous Nick Mehta said...

Nice job of connecting traditional HA techniques with cloud computing!

-Nick Mehta

7:39 PM  
Blogger techmonster said...

Neat Mukul - Thanks for writing such a comprehensive post.

8:45 PM  
Anonymous Michael Sheehan said...

Great post! Hope you don't mind, I used your images on the GoGrid blog to highlight the importance of Cloud Availability. Post is here.

-Michael Sheehan

9:23 PM  
Blogger kamlavati said...

Get Dedicated Server and Cloud Server Hosting Services backed by 24X7 Technical Support, Uptime Guarantee & Fanatical

support at Chillyz.com

12:58 PM  
Blogger Timmy said...

Nice information. Thanks for sharing it here. By the way have you heard about Cloudslam 2010 conference which the 2nd annual and virtual conference covering latest trends and innovations of Cloud Computing and its technologies. I hope this would be an good opportunity to gather more information on Cloud Computing and its technologies.

2:53 PM  
Blogger Naresh said...

Nice Post

2:15 PM  
Blogger Chris said...

Check out the performance of these Cloud Services at www.CloudSleuth.net it is a free service showing all of the major public cloud services and thier performance from all over the world!

1:50 PM  
Blogger Dissertation Writing Help said...

your post is nice . . let me tell u one thing that Blogs have become latest and important source of quality free information on net people enjoying for hours together. . .nice blog keep sharing;)
Dissertation Writing Services

7:58 PM  
Anonymous Cloud Hosting India said...

Hello,
Nice blog i like it
Cloud Hosting India has innumerable benefits to offer with safety and innovation being on top of the list.

11:57 AM  
Blogger Cloud Hosting India said...

Hello,
Nice blog i like it
Cloud hosting is considered the hottest and most reliable hosting solution that can eliminate a lot of hosting problems and difficulties.

Cloud hosting india

2:39 PM  
Anonymous cloud hosting india said...

Tremendous blog post, loads of beneficial information. I am about to show my buddies and ask them what they think.

12:27 PM  
Blogger Cloud Hosting India said...

Hello,
These servers offer tremendous capability of scalability and the facility to transfer data from one server of the network to another.

cloud hosting india

12:27 PM  
Blogger Harry Luke said...

Thanks for sharing. I am agree with your article. Cloud Hosting India is a good idea to increase the performance of website.

3:16 PM  
Blogger CloudWays said...

This comment has been removed by the author.

9:54 PM  

Post a Comment

Links to this post:

Create a Link

<< Home