E-Book MANAGING A MULTI-CLOUD ENVIRONMENT July 2016 MATCHING APPS WITH CLOUD PROVIDERS Businesses looking to shift applications to cloud services need to consider factors such as legacy infrastructure, application architecture and the need for global reach. It’s also important to examine the strengths and weaknesses of cloud providers before making any migration decision. BY KURT MARKO DGrowing Market DBreaking Down Billing Models DCloud Native vs. Traditional Apps DApplications Drive Service Selection DCloud Providers’ Parallels MANAGING A MULTI-CLOUD ENVIRONMENT Home Growing Market Cloud Native vs. Traditional Apps Cloud Providers’ Parallels Breaking Down Billing Models FTER YEARS OF existing vendor relationships, regulatory requirements and foot-dragging, the need for global reach and distribution. Applications Drive most IT orga- To be successful, an organization needs to look closely at Service Selection nizations have the details about the capabilities, advantages and similari- concluded that ties of the major IaaS providers. Plus, decision makers will resistance to cloud infrastructure is futile. Industry giants want to evaluate the options in light of their existing and Amazon Web Services (AWS) and Microsoft Azure are ap- planned application portfolio. proaching sales of a billion dollars a month and announcing commitments by major business converts such as Capital One,A GE and Netflix to move business IT operations to in- GROWING MARKET frastructure as a service (IaaS). Though the worldwide market for cloud infrastructure is Now the question for most IT organizations isn’t if it still quite fragmented, a handful of vendors garner just over should use cloud services, but when, where and which ones. half the total revenue: Amazon Web Services (AWS), Google Knowing when to use cloud computing is a matter of corpo- Cloud, IBM Softlayer, Microsoft Azure and Salesforce. Fig- rate strategy and IT cloud maturity. But determining where ures compiled by Synergy Research show that AWS alone and which services—namely the list of applications to mi- owns about one-third of the IaaS market, while both Azure grate and cloud providers to adopt—is dependent on myriad and Google are growing annually at triple-digit rates. factors, including legacy infrastructure, private/hybrid AWS, Azure and Google Cloud are the best options in a cloud plans, application architecture, service requirements, multi-tenant, public cloud infrastructure. IBM, meanwhile, 2 MATCHING APPS WITH CLOUD PROVIDERS MANAGING A MULTI-CLOUD ENVIRONMENT Home Growing Market provides an interesting mix of an open source IaaS, IBM vendors have added richer, higher-level features such as platform as a service (PaaS) and hosted bare metal servers. machine learning, business intelligence (BI), streaming data Cloud Native vs. With IBM’s use of OpenStack for IaaS and hybrid cloud, one ingestion (IoT), mobile app backends and serverless, event- Traditional Apps could lump it into the broader OpenStack public cloud eco- driven microservices to their portfolios. The result is con- system, e.g., Dreamhost, Internap, Rackspace and others. siderable overlap between products such as AWS or Azure Cloud Providers’ Parallels However, IBM has a much richer portfolio than those other and traditional pure-play PaaS products such as Cloud options. Foundry (Pivotal and IBM Bluemix), Force.com and Heroku Breaking Down VMware—given its dominant position as the virtualiza- (Salesforce) or OpenShift (Red Hat). Billing Models tion platform of choice in business data centers—is also Although AWS and Azure don’t draw sharp distinctions worth mentioning because of its vCloud Air product and between their infrastructure and platform services, Google Applications Drive network of service partners. VMware’s vCloud illustrates (App Engine) and IBM (Bluemix) do, with clearly identified Service Selection an important distinction between public cloud services: and branded PaaS stacks. Blending IaaS and PaaS services the level of support for hybrid deployments. Although all means the selection of a cloud provider is no longer IT’s vendors provide ways of securely connecting private infra- alone, since it’s not a choice solely about infrastructure. In- structure and public resources, AWS and Google are notable deed, with the growing variety and sophistication of applica- for only being available as shared services. In contrast, tion services, along with alternative deployment vehicles OpenStack, vCloud and, by the end of 2016, Azure can be such as app containers and event-driven compute services, deployed and managed by internal IT. This public-private/ developers play an increasingly important, and perhaps hybrid dichotomy is an important decision criterion. central, role in evaluating and selecting cloud providers. Although Salesforce has some sophisticated application development services, it’s primarily used as a packaged ap- plication, i.e., SaaS, rather than an application platform CLOUD NATIVE VS. TRADITIONAL APPS (PaaS). Salesforce can thus be seen as qualitatively different A fundamental factor when evaluating cloud providers is the from the other four cloud leaders. type of applications planned for cloud deployment. Indeed, Infrastructure and platform services were once consid- it illustrates the role developers must play in the selection ered well-defined and distinct service paradigms in the XaaS process because the cloud is far more than a new deploy- (anything as a service) hierarchy. Over time, traditional IaaS ment location. Jeffrey Snover, Microsoft’s chief architect for 3 MATCHING APPS WITH CLOUD PROVIDERS MANAGING A MULTI-CLOUD ENVIRONMENT Home Growing Market enterprise cloud, wrote on the company’s website in 2015 shared infrastructure and thus quickly deployed, moved that cloud is “a way of building and running infrastructure and scaled. In contrast, legacy, client-server applications are Cloud Native vs. that prioritizes speed and [empowers] developers to do built assuming ownership of an entire OS. They are shoe- Traditional Apps their best work.” horned into shared infrastructure via hypervisors and VMs; Whether you call it cloud-native or third platform, cloud in other words, they can run on, but aren’t built for, the cloud. Cloud Providers’ Parallels services have ushered in new ways of designing, partition- This architectural distinction has profound implica- ing, scaling, testing and deploying applications that are tions on the type of cloud service that’s best for a particular Breaking Down profoundly different from those in the prior client-server organization. Some products mimic the VM environment Billing Models (second platform) and mainframe (first platform) eras of IT. of internal data centers; others are mostly a collection of Cloud-first, greenfield apps are extremely modular. They RESTful services and APIs that can be mashed up into any Applications Drive are built around cloud services and API calls, designed for type of application. A prime example of the contrasting Service Selection How Traditional vs. Cloud-Native Apps Differ TRADITIONAL CLOUD-NATIVE monolithic modular and service-oriented run as a VM a collection of containers and services scale-up architecture scale-out architecture difficult to install, configure and deploy easily automated, moved and scaled extensive use and modification of existing largely self-contained data usage with batch on-premises data sets updates to legacy systems 4 MATCHING APPS WITH CLOUD PROVIDERS MANAGING A MULTI-CLOUD ENVIRONMENT Home Growing Market approaches is the bifurcation of EMC/VMware’s private CLOUD PROVIDERS’ PARALLELS cloud product line. Its Enterprise Hybrid Cloud based on The major cloud vendors are fiercely competitive. Even so, Cloud Native vs. vSphere is designed for traditional applications, while the when looked at as a bundle of compute, storage, network, Traditional Apps Native Hybrid Cloud—released in May 2016— targets next- data, application, security and management services, they generation, modular, microservice-based designs. have more in common than not. Since AWS is the top dog, Cloud Providers’ Parallels The dichotomy carries over to the public cloud when with the most customers and deepest service portfolio, it looking at the varying ways people use AWS. By offering effectively sets the standard others attempt to match. It’s a Breaking Down basic compute (Elastic Compute Cloud), storage volumes challenge, since AWS is constantly releasing new services Billing Models (Elastic Block Store), file systems (EFS) and private net- and enhancing existing ones, but Azure, Google and IBM works (VPC), AWS can be made to look like a bunch of VMs have advantages in certain situations. Applications Drive and network-attached storage running in a private data cen- The AWS portfolio is divided into three categories with 12 Service Selection ter. That would be perfect for legacy databases and server- focus areas: based applications. However, AWS can also be a platform for applications that are infrastructure agnostic and based on ■■Core Infrastructure: VMs, containers, storage (object, higher-level services like NoSQL databases, BI processing, block, file), database (relational, NoSQL, caching) and net- Hadoop-like clusters, message queues, push notification working (VPNs, DNS, load balancing) services, media transcoders and search engines. With these contrasts in mind, when thinking about cloud ■■Application Platform: data analytics (BI, machine learn- providers, consider the type of applications you’ll deploy