Having attended the OpenStack Design Summit this week and at the same time fielding calls from Forrester clients affected by the Amazon Web Services (AWS) outage, an interesting contrast in approaches bore out. You could boil it down to closed versus open but there’s more to this contrast that should be part of your consideration when selecting your Infrastructure as a Service (IaaS) providers.
The obvious comparison is that AWS’ architecture and operational procedures are very much their own and few outside the company know how it works. Not even close partners like RightScale or those behind the open source derivative Eucalyptus know it well enough to do more than deduce what happened based on their experience and what they could observe. OpenStack, on the other hand, is fully open source so if you want to know how it works you can download the code. At the Design Summit here in Santa Clara, Calif. this week, developers and infrastructure & operations professionals had ample opportunity to dig into the design and suggest and submit changes right there. And there were plenty of conversations this week about how CloudFiles and other storage services worked and how to ensure an AWS Elastic Block Store (EBS) mirror storm could be avoided.
It seems that during every major shift in the telecommunications, service provider or hosting market there is a string of moves like these as players attempt to capitalize on the change to gain greater market position. And there are plenty of investors caught up in the opportunity who are willing to lend a few bucks. In the dot.com period, through 2000s, we saw major shifts in the service provider landscape as colo/hosting giants were created such as Cable & Wireless and Equinix.
But what does this mean for infrastructure & operations professionals looking to select a hosting or Infrastructure as a Service (IaaS) cloud provider? The key is in determining if 1 + 1 actually equals anything greater than 2.
. . . 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.
What is it that you think makes one tech company stand out from another? “My product is better than your product”? Not anymore. “My salespeople are better than your salespeople”? Possibly. “My channel is better than your channel”. You’re getting warmer. How about, “My marketing machine is better than your marketing machine”?
For example, 41% of customers identify “the vendor’s (not including its salespeople’s) ability to understand our business problem”, compared with only 21% who identified “the vendor’s salesperson’s ability to understand our business problem” as the most important vendor action factor when selecting a tech vendor. Marketing is clearly the difference-maker.
But cloud computing changes everything. The implications of cloud computing go far beyond its technology delivery/consumption model. It seems I get questions from tech marketers about all things cloud these days. A few examples:
“How can I use the cloud more effectively to market our solutions?” (Answer: It’s not what you read in USA Today about Facebook and Twitter. According to the results of our 2011 B2B Social Technographics® survey, discussion forums and professional social networking sites (read: not consumer social sites) outpace Facebook and Twitter ten-fold as information sources for informing businesses’ technology purchase decisions.)
The lines are blurring between software and services — with the rise of cloud computing, that trend has accelerated faster than ever. But customers aren’t just looking at cloud business models, such as software-as-a-service (SaaS), when they want more flexibility in the way they license and use software. While in 2008 upfront perpetual software licenses (capex) made up more than 80% of a company’s software license spending, this percentage will drop to about 70% in 2011. The other 30% will consist of different, more flexible licensing models, including financing, subscription services, dynamic pricing, risk sharing, or used license models.
Forrester is currently digging deeper into the different software licensing models, their current status in the market, as well as their benefits and challenges. We kindly ask companies that are selling software and/or software related services to participate in our ~20-minute Online Forrester Research Software Licensing Survey, letting us know about current and future licensing strategies. Of course, all answers are optional and will be kept strictly confidential. We will only use anonymous, aggregated data in our upcoming research report, and interested participants can get a consolidated upfront summary of the survey results if they chose to enter an optional email address in the survey.
A lot has been written about potential threats to Intel’s low-power server hegemony, including discussions of threats from not only its perennial minority rival AMD but also from emerging non-x86 technologies such as ARM servers. While these are real threats, with potential for disrupting Intel’s position in the low power and small form factor server segment if left unanswered, Intel’s management has not been asleep at the wheel. As part of the rollout of the new Sandy Bridge architecture, Intel recently disclosed their platform strategy for what they are defining as “Micro Servers,” small single-socket servers with shared power and cooling to improve density beyond the generally accepted dividing line of one server per RU that separates “standard density” from “high density.” While I think that Intel’s definition is a bit myopic, mostly serving to attach a label to a well established category, it is a useful tool for segmenting low-end servers and talking about the relevant workloads.
Intel’s strategy revolves around introducing successive generations of its Sandy Bridge and future architectures embodied as Low Power (LP) and Ultra Low Power (ULP) products with promises of up to 2.2X performance per watt and 30% less actual power compared to previous generation equivalent x86 servers, as outlined in the following chart from Intel:
So what does this mean for Infrastructure & Operations professionals interested in serving the target loads for micro servers, such as:
The drum continues to beat for converged infrastructure products, and Dell has given it the latest thump with the introduction of vStart, a pre-integrated environment for VMware. Best thought of as a competitor to VCE, the integrated VMware, Cisco and EMC virtualization stack, vStart combines:
I had the pleasure earlier this week of attending Lawson Software’s conference and user exchange, aka CUE, in Boston.
The midmarket ERP apps vendor had the singular misfortune to throw its annual user party at a time of great uncertainty for both Lawson and its customers. Lawson has yet to respond to an unsolicited $1.8 billion acquisition offer from ERP rival Infor, aside from acknowledging receipt of the offer on March 11. Despite the Infor elephant in the room, CUE was a good-humored affair. Lawson execs exhibited grace under fire while customers expressed concern but remained cheerfully stoic and pragmatic.
Do you think Lawson will end up part of Infor? Alternatively, will it remain independent or will it be bought by a private equity firm and no longer be publicly traded à la Epicor? As apps vendors try to navigate fluctuating revenue mixes — rising subscriptions versus falling maintenance — being privately held may prove to be an attractive option.
Lawson is currently evaluating whether to break out subscription revenue as a separate line item in its next fiscal year. Of its 4,500 largely on-premise customers, around 350 use a Lawson SaaS product, the fruit of purchases such as Enwisen and Healthvision. Like other apps players, Lawson’s embraced Amazon.com’s EC2 as the cloud infrastructure for its HCM, M3 and S3 ERP apps. Several Lawson cloud services early adopters at CUE talked about their organizations’ experiences and there were some similarities in those stories:
They faced hardware refreshes and/or obsolescence of the app and database versions they used
They were already successfully running third-party SaaS apps or remotely hosted software
They used Lawson managed services as a steppingstone between the on-premises and cloud services worlds
Are you under increasing pressure from your business colleagues and sponsors to deliver more business value, faster, with higher quality? Have you been experimenting with new processes like Agile and new technologies like cloud as ways of meeting those objectives? Are you looking to transform your delivery capability, whether top-down or bottom-up?
If you answered yes to any of these questions, then you should pursue this special opportunity, which is open to all: next Tuesday, April 12, at 11 a.m. Eastern, I'll be delivering a webinar on Transforming Application Delivery, together with my colleague Diego Lo Giudice. Diego is one of the authors of our recent report on this topic, together with Dave West. I edited this report. I hope you can join us!
The world of hyper scale web properties has been shrouded in secrecy, with major players like Google and Amazon releasing only tantalizing dribbles of information about their infrastructure architecture and facilities, on the presumption that this information represented critical competitive IP. In one bold gesture, Facebook, which has certainly catapulted itself into the ranks of top-tier sites, has reversed that trend by simultaneously disclosing a wealth of information about the design of its new data center in rural Oregon and contributing much of the IP involving racks, servers, and power architecture to an open forum in the hopes of generating an ecosystem of suppliers to provide future equipment to themselves and other growing web companies.
The Data Center
By approaching the design of the data center as an integrated combination of servers for known workloads and the facilities themselves, Facebook has broken some new ground in data center architecture with its facility.
At a high level, a traditional enterprise DC has a utility transformer that feeds power to a centralized UPS, and then power is subsequently distributed through multiple levels of PDUs to the equipment racks. This is a reliable and flexible architecture, and one that has proven its worth in generations of commercial data centers. Unfortunately, in exchange for this flexibility and protection, it extracts a penalty of 6% to 7% of power even before it reaches the IT equipment.