Welcome!

Microservices Expo Authors: Liz McMillan, Flint Brenton, Jason Bloomberg, Elizabeth White, Yeshim Deniz

Related Topics: @CloudExpo, Microsoft Cloud

@CloudExpo: Article

Amazon, Google, Microsoft - Big Three Cloud Providers Examined

GOOG very much believes that the web is the platform; we have a divergent opinion

Brandon Watson's "Many Niches" Blog

There’s been quite a bit of chatter on the web about the Azure Services Platform. Obviously I’m excited to see people talking about our new platform, especially when there is plenty of good, some bad, and some good if not somewhat rambling. There will be no shortage of guessing as to what Microsoft is “really up to” with our development efforts.

I wanted to take a crack at that one, but from a completely different perspective. I want to frame the discussion centered on the motivations of the platform providers, and let that be a guide to understanding the delivered product.

Amazon
Let me start by giving a hat tip to the AMZN guys. Their web services platform (AWS) has really been at the tip of the spear for cloud computing. or the sake of this discussion, when I use the term “cloud computing,” I am talking about the developer platform, not things like GOOG apps. The AMZN services are a loosely coupled set of services targeted at developers looking to avail themselves of infrastructure buildout. Their infrastructure as a service (EC2) is a great way for developers to reduce their capital expenditures and take on a variable costing model for their servers.

The services, all up, encompass several key pieces for building applications that can take on a range of workloads. The ability to now run Windows Server 2003 (which should get you terminal services) means that as a developer, you can deploy varying application types into AWS, beyond simply web apps. From a developer standpoint, however, there is no unified development experience. Which brings me to the discussion around motivations.

AMZN essentially spends 10 months out of the year building out servers. They build out massive numbers of servers for the two months out of the year when they are handling the Christmas shopping season. AMZN is, for all intents and purposes, a giant mall. They spend hundreds of millions of dollars a year building more capacity for their mall. Their store is the primary reason shoppers come in the front door, and most of the year, their mall is empty, relative to the size of the mall. As a retailer with an ecommerce backend, their problems are no different than most enterprises. They have machines that are sitting around doing little or nothing for large portions of the year. Unlike most other enterprises, AMZN has the financial capacity to build out their server capacity. At some point, AMZN made the decision to no longer be the primary traffic draw to their mall. They realized that they could completely offset their own traffic (and then some) by taking the technology that they had built for themselves and making it available to other developers.

AMZN is, essentially, in the load management business. They are a low margin retail operator that is running a hugely expensive infrastructure for which they are seeking maximum utilization. They would like nothing more than to be noise in their own system. AMZN is relentlessly metrics driven. As such, they have a pretty good idea of how much money to expect off of traffic that walks through their front door. They know how much to expect from traffic ending up at one of their marketplace partners. With the addition of AWS, they have a new way to monetize their capacity, and with their predictable pricing model, they know exactly how much money they are going to make off of customers who deploy applications to their service.Traffic on their network makes them money. It may not make your app money, but it makes them money, so they are happy. It more than likely saves you money, so you are probably happy too.

So, AMZN is motivated by maximization of infrastructure capacity, and optimization of what would otherwise be very low margin businesses. They do this by delivering a loosely coupled set of services to developers looking for infrastructure as a service. They aren’t necessarily targeting developers. They aren’t a platform, per se. They are targeting anyone who is looking to move workloads off of their own infrastructure and onto AMZN.

Google
Ahh, Google. I love those guys. They have done plenty of cool things, and their release of the AppEngine (GAE) was welcomed with very loud praise from many in the tech community. According to some reports, they had 25,000 developers sign up for GAE in the first few hours of releasing it.Taken as a whole, GAE is a very tightly coupled set of services designed to allow developers to build applications that will have no problem scaling up to, theoretically, infinite capacity. The rigid requirements for a developer deploying into the GAE are such that you use one language (Python) and their database (big table).

Once again, when considering what has been built, one need look no further than the motivations of GOOG to really get where they are going. When you consider the stricture imposed on the architecture of apps built for GAE (singple process, no long running queries, no local file access, no network access), a developer is all but required to build standard CRUD web applications. There is no stack for enterprise integration. The delivery vehicle is the web browser. The data that is created goes right into big table.

Some might say that GOOG’s core business is search. I actually have a different opinion. GOOG’s core business is the monetization of page views. Search is their instantiation of that business model, but many of their other applications have nothing to do with search, and everything to do with the monetization of page views. Think about gmail - ads on the sidebar.

Applicaitons on GAE are mostly CRUD apps, storing structured data into big table. As a developer, building an applicaiton on GAE, you are essentially feeding the GOOG beast. While they have not yet released final pricing, allow me to put on my pointy tin foil hat and talk about what might come to pass. GOOG knows exactly how much it costs to run their infrastructure, and as such could hand developers a bill for the resources which they consume. However, GOOG doesn’t have AMZN’s problem. Their traffic is mostly linear, and going up and to the right. It’s probably logarithmic at this point, but who’s counting? In any event, since they have little variability in their traffic patterns, they don’t have to get into the load management business. By allowing developers to build applications on their infrastructure, they are incurring unnecessary costs. Their motivations, however, are driven by their business model. Each new app that is plugged into the infrastructure ads new data to their data set, and creates new opportunities for page monetization.

Think of the case where GOOG shows up to a developer and says, “hey, moboganda.com - how are you doing? That’s a great app you put up on GAE. We’ve been going over the data and we figured out that if we ran AdSense on your pages 20% of the time, we could actually recoup the cost of running the infrastructure for you. In fact, you don’t even need to do anything, since we own the infrastructure, the feature is already in there. You can turn it off with a JavaScript include.” As the young CEO of a web startup, this could sound like a pretty cool deal. Free infrastructure and they didn’t have to do anything to get that turned on. Not bad. Let’s take this game of what-if one step further. The GOOG guys come back in two months with the following, “hey buddy, that app of yours is performing really well. You made more money on those 20% ads than we thought. What we would love to do is run ads 100% of the time. Of course, you are free to sell that ad space yourself. I’m sure you have a full time ad sales force. We’re only a multi-billion dollar company focused soley on monetizing pageviews, but feel free to go it alone if you want.” To the developer, this could be music to your ears - focus on building the application, and GOOG does the monetization for you. If you really wanted to go crazy, one could imagine a world where GOOG says to their developers, “$5 bounty for all new GOOG accounts created through your app.”

Bottom line: GOOG is motivated by feeding the GOOG beast and monetizing pageviews. That shines through in the design of their app delivery vehicle, the tight coupling of the services, and the expected design patters of the applications to be built on their infrastructure.

Microsoft
With all of the above points in mind, hopefully you can start drawing some pretty good conclusions about the potential future directions of the competitive cloud platforms in the market. As for MSFT, there are plenty of things I could say, but let me simply state what I believe to be our motivations. We are a platform company. We very much believe that we are in the business of delivering the best platform and tools to developers to build great applications. Our on-premise stack has proven to be extremely successful over the last several decades. With the release of the Azure Services Platform, one of the core design tenets was that we would like to achieve parity between our on and off-premise stacks. The entirety of the Azure Services Platform is designed to enable experienced MSFT developers to be combat effective on day one.

However, the platform, from my point of view, is but a part of the engine. The heart of the engine is the application that you plan to build. GOOG very much believes that the web is the platform, and thus the web browser is the only delivery vehicle for applications. We have a divergent opinion. It seems absolutely crazy to me that a person carries around more computing power in their pocket today (cell phone) than was available a scant 15 years ago in the high end desktop computers, and GOOG believes that those processor cycles should be shunted aside. Our software plus services strategy really is about enabling developers to deliver the right experience to their customers, on the preferred end point device, at the right time from a single piece of infrastructure. We are motivated by our developers building great applications, and Azure is the final leg of the software plus services strategy.


[This post appeared originally here and is republished in full with the kind permission of the author.]

More Stories By Brandon Watson

Brandon Watson is Director for Windows Phone 7. He specifically focuses on developers and the developer platform. He rejoined Microsoft in 2008 after nearly a decade on Wall Street and running successful start-ups. He has both an engineering degree and an economics degree from the University of Pennsylvania, as well as an MBA from The Wharton School of Business, and blogs at www.manyniches.com.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes a lot of work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reduction in cost ...
Don’t go chasing waterfall … development, that is. According to a recent post by Madison Moore on Medium featuring insights from several software delivery industry leaders, waterfall is – while still popular – not the best way to win in the marketplace. With methodologies like Agile, DevOps and Continuous Delivery becoming ever more prominent over the past 15 years or so, waterfall is old news. Or, is it? Moore cites a recent study by Gartner: “According to Gartner’s IT Key Metrics Data report, ...
Your homes and cars can be automated and self-serviced. Why can't your storage? From simply asking questions to analyze and troubleshoot your infrastructure, to provisioning storage with snapshots, recovery and replication, your wildest sci-fi dream has come true. In his session at @DevOpsSummit at 20th Cloud Expo, Dan Florea, Director of Product Management at Tintri, provided a ChatOps demo where you can talk to your storage and manage it from anywhere, through Slack and similar services with...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Archi...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Without a clear strategy for cost control and an architecture designed with cloud services in mind, costs and operational performance can quickly get out of control. To avoid multiple architectural redesigns requires extensive thought and planning. Boundary (now part of BMC) launched a new public-facing multi-tenant high resolution monitoring service on Amazon AWS two years ago, facing challenges and learning best practices in the early days of the new service.
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that e...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
We all know that end users experience the Internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices – not doing so will be a path to eventual b...
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
"DivvyCloud as a company set out to help customers automate solutions to the most common cloud problems," noted Jeremy Snyder, VP of Business Development at DivvyCloud, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
In his session at Cloud Expo, Alan Winters, U.S. Head of Business Development at MobiDev, presented a success story of an entrepreneur who has both suffered through and benefited from offshore development across multiple businesses: The smart choice, or how to select the right offshore development partner Warning signs, or how to minimize chances of making the wrong choice Collaboration, or how to establish the most effective work processes Budget control, or how to maximize project result...