Slashdot Mirror
Microsoft Will Be Largest Infrastructure As A Service Vendor By 2019, Says Morgan Stanley Survey (geekwire.com)
An anonymous reader writes from a report via GeekWire: According to Morgan Stanley's 2016 CIO Survey of 100 CIOs (75 CIOs based in the U.S., and 25 based in Europe), Microsoft's Azure will overtake Amazon Web Services (AWS) by 2019 to become the largest Infrastructure as a Service (IaaS) and Platform as a Service (PaaS). The survey finds that roughly 31 percent of the CIOs will be using Azure for IaaS, compared to roughly 30 percent using AWS. Today, roughly 21 percent are using AWS and 12 percent are using Azure. According to the survey, Azure is already leading AWS in PaaS, used by about 18 percent of the respondents, versus AWS's 16 percent. Azure's lead will grow slightly by 2019, growing 9.8 percent versus 6.4 percent. Nearly 30 percent of all applications will be migrated to the public cloud by the end of 2017, up from 14 percent today, the survey said. On-premises apps will decline to 58 percent, from 71 percent today. Predictably, hardware vendors, including conventional and flash storage makers, will continue to suffer as their market is eaten by the cloud. Hardware spending growth is down this year to 3.2 percent, from 3.4 percent last year. Microsoft recently announced it will be entering the legal marijuana industry. It will partner with Los Angeles-based startup Kind on a system for tracking the legal growing and sale of marijuana, with Microsoft powering the software through its Azure cloud computing service.
Having used both Azure and AWS, I can honestly say that AWS is light years ahead of Azure...
Azure storage services has got some awesome consistency guarantees.. But it won't scale like S3, not in terms of requests, throughput or features.
Microsoft has an abyssal story for authorization and access policies... There is nothing like IAM that crosses all services, some services have policies, other services you get shared secrets (to be shared between all users)..
Honestly, they can't even figure out to make a consistent naming policy between different storage services... Figuring out what characters is allowed in names of fields, resources, urls, etc. is a nightmare... Even with azure storage services (queue, table and blob) they have vastly different restrictions... It's a joke.
The only thing interesting with Azure is their table storage service, price and simplicity wise it's a joy. But given how bad everything else, I'm tempted to move my stuff to AWS and pay a bit more for dynamodb...