Amazon Web Services (AWS) held its first global customer and partner conference, re:Invent, in late November in Las Vegas, attracting approximately 6,000 attendees. While aimed squarely at developers, AWS highlighted two key themes that will appeal directly to enterprise IT decision-makers:
Continued global expansion. AWS cites customers in 190 countries, but the company is clearly pushing for greater penetration into enterprise accounts via aggressive global expansion. AWS now has nine regions (each of which has at least one data center), including three in Asia Pacific: Tokyo, Singapore, and Sydney.
An expanded services footprint within customer accounts. The major announcement at re:Invent was a limited preview of a new data warehouse (DW) service called Amazon Redshift — a fully managed, cloud-based, petabyte-scale DW. As my colleague Stefan Ried tweeted during the event, with a limit of 1.6 petabytes, this is not just for testing and development — this is a serious production warehouse.
Is your cloud strategy centered on saving money or fueling revenue growth? Where you land on this question could determine a lot about your experience level with cloud services and what guidance you should be giving to your application developers and infrastructure & operations teams. According to our research the majority of CIOs would vote for the savings, seeing cloud computing as an evolution of outsourcing and hosting that can drive down capital and operations expenses. In some cases this is correct but in many the opposite will result. Using the cloud wrong may raise your costs.
But this isn’t a debate worth having because it’s the exploration of the use cases where it does save you money that bears the real fruit. And it’s through this experience that you can start shifting your thinking from cost savings to revenue opportunities. Forrester surveys show that the top reasons developers tap into cloud services (and the empowered non-developers in your business units) is to rapidly deploy new services and capabilities. And the drivers behind these efforts – new services, better customer experience and improved productivity. Translation: Revenues and profits.
If the cloud is bringing new money in the door, does it really matter if it’s the cheaper solution? Not at first. But over time using cloud as a revenue engine doesn’t necessarily mean high margins on that revenue. That’s where your experience with the cost advantaged uses of cloud come in.
. . . but bad reactive marketing can make the problem much worse.
[co-authored by Zachary Reiss-Davis]
As has been widely reported, in sources broad and narrow, Amazon.com’s cloud service EC2 went down for an extended period of time yesterday, bringing many of the hottest high-tech startups with it, ranging from the well known (Foursquare, Quora) to the esoteric (About.me, EveryTrail). For a partial list of smaller startups affected, see http://ec2disabled.com/.
While this is clearly a blow to both Amazon.com and to the cloud hosting market in general, it also serves as an example of how technology companies must quickly respond publicly and engage with their customers when problems arise. Amazon.com let their customers control the narrative by not participating in any social media response to the problem; their only communication was through their online dashboard with vague platitudes. Instead, they allowed angry heads of product management and CEOs who are used to communicating with their customers on blogs and Twitter to unequivocally blame Amazon.com for the problem.
Cloud infrastructure-as-a-service (IaaS) is a hot market. Amazon Web Services, now five years old, drives a lot of attention and customer volume, but the vendor strategists at enterprise-facing providers such as IBM, HP, AT&T and Verizon have been building and delivering IaaS offerings. As I’ve studied the market, I’ve heard wildly different types of requirements from buyers and quite a range of offerings from service providers. Yet much of the industry dialogue is about one central idea of what IaaS is – think that’s wrong headed. I found that there were really two buyer types: 1) informal buyers outside of the IT operations/data center manager organizations, such as engineers, scientists, marketing executives, and developers, and 2) formal buyers, the IT operations and data center managers responsible for operating applications and maintaining infrastructure.
With this idea in mind, I set out to test the views of IT infrastructure buyers in the Forrsights Hardware Survey, Q3 2010 and learned that:
After 2+ years of cloud hype, only 6% of enterprises IT infrastructure respondents report using IaaS, with another 7% planning to implement by Q3, 2012. After flat adoption from 2008 to 2009, this represents an approximate doubling from 2009, off a very small base.
Almost two thirds of IT infrastructure buyers themselves don’t believe they are the primary buyer of cloud IaaS! We asked them which groups in their company are using or most interested in cloud IaaS. Only 36% of IT infrastructure buyers listed themselves, while 7% didn’t know. The rest, 58% said that IT developers, Web site owners, business unit owners of batch compute intensive apps, and other business unit developers were more interested in using IaaS than themselves.
This week Amazon Web Services announced a new pricing tier for its Elastic Compute Cloud (EC2) service and in doing so has differentiated its offering even further. At first blush the free tier sounds like a free trial, which isn't anything new in cloud computing. True, the free tier is time-limited, but you get 12 months, and capacity limited, along multiple dimensions. But it's also a new pricing band. And for three of its services, SimpleDB, Simple Queueing Service (SQS), and Simple Notification Service (SNS) the free tier is indefinite. Look for Amazon to lift the 12 month limit on this service next October, because the free tier will drive revenues for AWS long term. Here's why:
A few weeks back I posted a story about how one of our clients has been turning cloud economics to their advantage by flipping the concept of capacity planning on its head. Their strategy was to concentrate not on how much capacity they would need when their application got hot, but on how they could reduce its capacity footprint when it wasn't. As small as they could get it, they couldn't shrink it to the point where they incurred no cost at all; they were left with at least a storage and a caching bill. Now with the free tier, they can achieve a no-cost footprint.