Google Groups

Re: [ Cloud Computing ] Re: 5 Key Lessons for Customers of the Cloud

CloudSigma Apr 23, 2011 11:22 PM
Posted in group: Cloud Computing
The military often get accused of fighting the last war or at least is in danger of doing so and we can look at things in the same light in the cloud right now. People's knee jerk reaction to the outage this week saw simple 'use multiple AWS zones' however this doesn't fully address the issue because AWS remains a single point of failure in this case. When it comes to this we very much 'eat our own dog food' by the way and do encourage all our customers to run secondary or balanced operations within another cloud provider.

There are a myriad of scenarios where not being reliant on one cloud provider (even in multiple locations) makes a lot of sense. Companies go under, get bought, change policies, change products, do things we don't like etc. There are therefore many practical, technical and ethical reasons why it is wise to be reliant on more than one cloud vendor. That is the next single point of failure that people will talk about.



On Sat, Apr 23, 2011 at 11:04 PM, Miha Ahronovitz <> wrote:
The opinions I express are mine. AWS is not a competition, and it is a competition. So is every company in the cloud space.  AWS. is a player, albeit the largest one, in what we preach on this forum: cloud computing.

The started it all and their failure can compromise the idea of cloud computing future adoption, in narrow minds  that abound, unfortunately around. . This makes us all friends with AWS. However their SLA - discussed here in depth -are not consumer friendly.

Sure, I think Amazon should tolerate 3rd party , sort of cloud disaster recovery. These 3rd parties, may use tools to migrate to safer locations of the provider (like from AWS East to West) or may have multiple providers under a single management.

But knowing how Amazon does things, they will probably develop in-house another Service , let's name it, ADR  (Amazon Disaster Recovery) and charge for it accordingly.

This is not a "non-relevant" functionality. After the AWS incident, it is highly relevant to offer services for cloud disaster recovery.


On 4/23/2011 12:06 PM, Khazret Sapenov wrote:

On Sat, Apr 23, 2011 at 2:58 PM, Miha Ahronovitz <> wrote:
Khazret, to give credibility to what you say, see
California EC is up, N. Virginia is down.

Thanks, Miha for enhancing credibility of my post, but I've posted this link already yesterday and it's referenced everywhere.
But why it should be the worry of the customers to move things
AWS should have mechanisms to move automatically to other facilities.
It doesn't

Your statement contradicts your employer's notion of IaaS providing only bare minimum with all 'non-relevant' functionality outsourced to external parties.
Now you want your competition to make an extra step, that sounds logical, but not implemented by many [IaaS] yet. 



On Apr 23, 11:46 am, Khazret Sapenov <> wrote:
> On Sat, Apr 23, 2011 at 1:09 PM, CloudSigma <> wrote:
> > Following the major outage that AWS suffered in their east coast US
> > facility this week, after the dust settles, what lessons can customers
> > actually learn from the events of this last week?
> > Here are the five key lessons we've highlighted to customers:
> > Lesson 1: Both Cloud and Dedicated Computing Have Single Points of
> > Failure
> > Lesson 2: Size is No Protection from Outages without Redundancy
> > Lesson 3: All Data Centres Are Not Equal
> > Lesson 4: The Price-Performance-Reliability Metric
> > Lesson 5: Achieving a highly robust set-up is cheaper and easier in
> > the Cloud
> > Customers need openness from vendors about their infrastructure
> > choices and locations in order to create price-performance-reliability
> > comparisons between clouds. This is a key development needed if people
> > are to make the right decisions and create the appropriate strategies
> > in line with their computing needs in the cloud.
> Customers already have wide choice of locations within Amazon EC2.
> If you saw their status of availability, only one location of many was
> affected,
> so if one has to engineer his/her apps for redundancy/resilience,
> then first quick and easy way would be to implement such DR functionality
> within one cloud (be it AWS or another provider, if they have multiple
> locations at all),
> where you have uniform interfaces and formats, so re-engineering efforts do
> not sacrifice reliability and interoperability of final solution.
> > Best wishes,
> > Robert
> > CTO
> > CloudSigma
> > Full test of our blog post on this subject can be found at

3rd Annual Cloud Slam 2011 Conference * April 18-22, 2011 * Mountain View, CA *
UP 2010 Conference:
Posting guidelines:
Follow us on Twitter @cloudcomp_group
Post Job/Resume at
Get hundreds of conference sessions and panels on cloud computing on DVD at,, or GET instant access to downloadable versions at
You received this message because you are subscribed to the Google Groups "Cloud Computing" group.
To post to this group, send email to
To unsubscribe from this group, send email to

Robert Jenkins
CloudSigma AG
Create a cloud server in 2 minutes:

This email is from CLOUDSIGMA AG. The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed to or used by or copied in any way by anyone other than the intended recipient. If this email is received in error, please contact CLOUDSIGMA AG on +41 (0)44 585 39 07 quoting the name of the sender and the email address to which it has been sent and then delete it. Please note that neither CLOUDSIGMA AG nor the sender accepts any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. CLOUDSIGMA AG is a public limited company registered in Canton Zürich, Switzerland (registered number CH- with registered offices at Sägereistrasse 29, 8152 Glattbrugg, Switzerland. For further information, please refer to .