The What, The Why, And the How of Hybrid Cloud - SME

8/17/2019 The What, The Why, And the How of Hybrid Cloud - SME

1/13

Osterman Research, Inc.P.O. Box 1058 • Black Diamond, Washington • 98010-1058 • USA

Tel: +1 206 683 5683 • [email protected]

www.ostermanresearch.com • twitter.com/mosterman

An Osterman Research White Paper

Published May 2016

The What, the Why andthe How of Hybrid Cloud

WHITEPAPER


2/13

©2016 Osterman Research, Inc. 1

The What, the Why, and theHow of Hybrid Cloud

EXECUTIVE SUMMARYWhen we think about “the cloud,” it’s natural to focus on public clouds. But public isnot the only type of cloud.

Public clouds use proven technology to pool data center resources and help maximizetheir computing potential. These same principles can be used in your data center,either on your premises or on one that you exclusively rent from someone else, tocreate a private cloud. This technology also gives you the flexibility to mix and match;

allowing you to choose where an application is hosted, and to move it later.

This then is the essence of hybrid cloud: With the benefit of cloud technology, youcan move workloads between public and private clouds — or choose a combination ofthe two.

The shift to hybrid cloud is all-but inevitable, so grasp the opportunity. It’s not amatter of “if” but of “when”.

ABOUT THIS WHITE PAPERIn this white paper we discuss what hybrid cloud is, why it’s inevitable, and how totake advantage of it. We look at some of the barriers to public-cloud adoption, whilewe cut through unnecessary technicalities to get to the heart of the matter. Wealso offer a brief overview of the sponsor of this paper and their relevant solutions.

WHAT HYBRID CLOUD ISCLOUD IS MORE THAN MERE HOSTED SOFTWAREPeople often think that “the cloud” is applications running in someone else’s datacenter, but there’s an important distinction to be made between hosted software-as-a-service (SaaS) and cloud.

• SaaS is generally focused on an application that runs in a vendor’s data center.In other words, it’s an application hosted elsewhere.

• Cloud has a unique set of benefits in addition to SaaS, and is based on a specifictype of architecture. This architecture consists of remote computing resources ,such as virtual servers, storage and the other elements of a computingenvironment, which differentiate it from simple hosting or SaaS and ultimatelyenables hybrid cloud (for an introduction to cloud technologies, see the sectionThe How of Hybrid Cloud ).

BUSINESS BENEFITS OF CLOUDHow can you tell it’s a true public cloud, and not just hosting or SaaS? Cloudtechnology permits several business benefits; here are our top five:

• Elasticity, or “on demand” Cloud allows the server “horsepower” applied to a workload to grow andshrink as the demand ebbs and flows. If it’s not elastic, it’s not cloud!

• Zero CapEx

Public cloud minimizes or eliminates up-front costs, such as the capitalexpenditure requirements for servers, load balancers, real estate and all ofthe other elements of an on-premises data center. Instead, the cloudprovider sweats its capital by charging you on a “pay-as-you-go” or utilitymodel.

• Low OpEx Cloud minimizes operating expenditures because of the inherent economiesof scale enabled by the technology.

This then is theessence of hybridcloud: With thebenefit of cloudtechnology, youcan moveworkloadsbetween publicand privateclouds — orchoose acombination ofthe two.


3/13



• Secure multi-tenancy Your workload can run alongside other workloads — which may or may notbe associated with your business. Each is completely independent of theothers, with assured security. This ability to securely share infrastructurewith other users is key to reducing cost.

• Fast failover Outages, natural disasters and other disruptive events happen — even in the

best IT shop. But cloud can allow workloads to move quickly from a faileddata center to a backup location, ensuring uptime close to 24x7. While notall cloud services explicitly include failover, customers can usually enable it.It’s typically far more expensive to use on-premises data centers for businesscontinuity.

SO WHAT MAKES A CLOUD A HYBRID CLOUD?It’s too limiting to think about “ The Cloud”. We’re now in the age of interconnected clouds. There are many public clouds to choose from, such as Amazon Web Services(AWS), IBM Softlayer, Microsoft Azure, or Google Cloud Platform. You can also build aprivate cloud in a data center that’s owned or rented by your organization — typicallyon your premises.

So a hybrid-cloud architecture allows IT to choose where data are located, and where

that data is processed. Not only can you choose whether to use a private or a publiccloud, you can also choose which public cloud to use. And you can revisit thosechoices, as situations change — for example, moving from public to private; forexample, from Amazon to Softlayer or OpenText.

Be aware there are varying ways to describe “public” and “private” in the cloudindustry. i Under one definition, private clouds can also be built and operated by acloud service provider — in a remote data center, or on your premises. ii This offerssimilar on-demand, zero-CapEx benefits to those of public cloud.

So a hybrid cloud uses a mix of public and private cloud resources. But which mix?

FOUR MAIN CLOUD CHOICE CRITERIAIn a hybrid cloud, IT will choose which cloud resources to use for a workload, aiming

to make the best selection. But what do we mean by “best”?

In brief, hybrid cloud allows IT to optimize for criteria that include:

• Total cost of ownership (TCO) One public cloud service might cost less for certain workloads than another.

And certain large-scale workloads could be less expensive in a private cloud.

• Performance Interactive workloads might not perform so well from a remote data center.So IT could prefer to host strategic workloads locally in a private cloud, whileplacing tactical workloads in a public cloud. (There’s more detail in thesection, The Laws of Physics .)

•

Scalability Public clouds tend to be more flexible when workloads grow unexpectedly orpeak temporarily. This is due to the pay-as-you-go model of most cloudservices. The other benefit of this flexible architecture is that OpEx falls withreduced usage.

• Regulation, risk and security You might need to keep certain workloads in a private data center. This needcould come from external regulation, or from your own risk assessment. Butsituations can change, so planning a hybrid-cloud architecture now allows

In a hybridcloud, IT willchoose whichcloud resourcesto use for aworkload, aimingto make the bestselection. But

what do we meanby “best”?


4/13



you to move workloads to a public cloud in the future.

(This is just a brief flavor; we’ll discuss these criteria and more in the nextsection.)

IN SUMMARYThink of hybrid cloud as a toolbox: The skill is to know which of the many tools in thebox to use, and when to switch tools — or even to use several tools at once.

In the survey we conducted for this white paper, IT managers saidregulation/risk/security is extremely important to inform their decision about siting aworkload. We asked users which of 14 criteria would affect their decision to site anapplication in either a private or public cloud, either positively or negatively.

Survey respondents felt strongly that regulation/risk/security would tend to dissuadethem from using a public cloud. But respondents also felt that many of those samecriteria are a positive for choosing private cloud, along with TCO. However, therespondents were split when asked about other criteria, with no significant trend ofopinion.

Figure 1 shows the top drivers perceived as negative for a public cloud choice.Concerns around the safety of sensitive and confidential data are the leading

negative drivers away from public cloud, with over half of respondents (56%)expressing it, while Figure 2 indicates that the majority of organizations (62%)believe the safety of sensitive and confidential information is a reason to adoptprivate cloud.

Figure 1Reasons Not to Choose a Public Cloud% Responding Negative Drivers Toward Public Cloud

Source: Osterman Research, Inc.

Figure 2 shows the top drivers perceived as positive for a private cloud choice (eitherrun by the organization’s IT team or by a third party on premises).

Think of hybridcloud as atoolbox: The skillis to know whichof the many toolsin the box to use,and when toswitch tools — oreven to useseveral tools atonce.


5/13



Figure 2Reasons to Choose a Private Cloud% Responding Positive Drivers Toward Public Cloud


We also asked users whether they thought their applications are more or less securein a public cloud, compared to a conventional, on-premises architecture. The surveyrespondents showed a preference for the security of an on-premises application, asshown in Figure 3. While a substantial proportion of survey respondents believe thecloud is less secure, it is important to note that most leading cloud providers enjoyeconomies of scale, as well as a reputation to defend. This means they can affordrobust physical and logical security capabilities more easily than most organizationsthat manage infrastructure on-premises.

Figure 3Perceptions About the Security of Applications Managed in a Public CloudRelative to those Managed On-Premises


While asubstantial proportion ofsurvey respon-dents believe thecloud is lesssecure, it isimportant to notethat most leadingcloud providersenjoy economiesof scale, as wellas a reputation todefend.


6/13



WHY HYBRID CLOUD IS INEVITABLEIn the previous section, we talked about the four main criteria IT can use to decidewhether a workload should be in a public or private cloud: cost, performance, scaling,and regulation/risk/security. In this section, we’ll look in more detail at why you mightchoose public, private or both.

APPLICATION LIFECYCLEPut simply, you can think of the lifecycle of an enterprise application in five typicalphases. Usually, each phase suggests a natural location for the workload:

• Prototyping and early development phaseInitial development work is typically done on-premises — often simplyrunning on developers’ own desktop machines, as opposed to “proper”servers. (A public cloud can also be appropriate, however.)

• Later development and Beta-test phase As development matures, and as components from several developers areintegrated, IT teams usually find it better to use a public cloud, to avoidCapEx — and to test that the workload can successfully be moved from onecloud to another. (It can sometimes be appropriate to use a private cloud,for example because of regulation.)

• Pilot and Gamma-test phaseInitial live use of the application by a small, select group of sympatheticusers will typically be in a public cloud. As part of this pilot phase, the ITteam can gain experience about how the application scales, which will helpdecide where the next phase should be sited. (Again, it can sometimes beappropriate to use a private cloud.)

• Majority production phaseThe main period of the application’s use, by the largest number of its users.During this phase, the application can be located in a public or a privatecloud, depending on our four main criteria and the other considerations we’lldescribe later.

• Legacy phaseMany enterprise applications remain important to a small group of users afterthey are otherwise “obsolete” — perhaps for archival purposes, or to servicea niche need. Typically, you’d run these legacy workloads in a public cloud,because of the desirability of service continuity at low cost.

In our survey, users broadly agreed with these natural locations. We asked users inwhich phases of its lifecycle they would be comfortable hosting an application in apublic cloud. We also asked about the phases for which they would never becomfortable using a public cloud.

Results broadly mirror our suggestions above. Survey respondents were very happyto use a public cloud for prototyping, development and pilot, but significantly lessinclined to host an application in a public cloud during the majority production phase.Indeed, the only phase when a significant number of respondents would never use a

public cloud is in majority production, as shown in Figure 4.

You can think ofthe lifecycle of anenterpriseapplication in

five typical phases. Usually,each phasesuggests a

natural location for the workload.


7/13



Figure 4Phases of the Application Lifecycle With Which Decision Makers Would beComfortable or Uncomfortable Using a Public Cloud


We also asked a series of other questions seeking respondents’ attitudes todeployment. The most notable conclusion: they are more likely to deploy on-premisesor in a private cloud if the application is considered “critical and internal-facing.”

Once a critical, customer-facing application had been thoroughly vetted and was fullyoperational, 38% of respondents told us they would deploy it in either a public orhybrid cloud; but for a critical, internal-facing application, only 22% would do so. Thissuggests many IT managers still aren’t fully confident that a public cloud can provide

the same quality of service or security as conventional deployments.It’s also notable that more than twice as many respondents said they were unsurehow they’d deploy a “thoroughly vetted and fully operational” application, comparedwith an initial deployment.

We also wanted to understand how organizations might choose to deploy anapplication, depending on the sensitivity of the information that it would manage. Asshown in Figure 5, organizations deploying systems that manage customer-facinginformation are open to deploying it in a public cloud initially — and even more soonce the system had been fully vetted. However, this is not the case for systems thatmanage highly confidential information, such as intellectual property, as shown inFigure 6.

[Organizationsare] more likelyto deploy on-

premises or in a private cloud ifthe application isconsidered“critical andinternal-facing.”


8/13



Figure 5Preferences for Deploying a Customer-Facing Application


Figure 6Preferences for Deploying a System That Manages Highly ConfidentialInformation or Intellectual Property


HYBRID CLOUD LETS YOU OPTIMIZE FOR TCOEvery public cloud provider prices its services differently to the others. And thoseprices can change, as can service quality. So, the ability to easily switch your cloudprovider is valuable protection against lock-in.

Every publiccloud provider

prices its servicesdifferently to theothers. And those

prices canchange, as canservice quality.


9/13



Naturally, the cost models of public and private cloud are completely different. As arough rule of thumb, a small-to-medium-sized workload on a public cloud service willcost significantly less than the equivalent workload in an on-premises, private cloudthat you own.

When you analyze the total cost-of-ownership (TCO) — including such line items asamortized capital costs, fully-loaded people costs, and the cost of power — aworkload typically needs to be extremely large for it to make financial sense to run itin-house. As workloads grow, there typically comes a “crossover” point, at which theTCO of private cloud is lower than public. A good example: Dropbox’s recentdisclosure that it has moved the bulk of its 500 petabytes of customer file storagefrom a public cloud to a custom, on-premises file system. The company made thismove because of favorable economics, compared with the public cloud it was usingpreviously. iii

It’s important to note that different cloud service providers have varying ways ofcharging for usage, including time-based accounting, network charges, tiered storagerates, etc., but that detail is beyond the scope of this paper.

From our survey, it’s clear that the IT decision makers and influencers we surveyedperceive TCO as one important driver of hybrid-cloud decisions. When asked aboutlocating an application in a public or a private cloud, TCO was a moderately positivecriterion (36%) and a weak negative one (12%).

HYBRID CLOUD PERMITS SPLIT USER POPULATIONSIT teams often wish to segment their users into two or more groups. Hybrid cloud isa good way to support this type of deployment, either by dividing users into private-and public-cloud groups, or by spreading them among more than one public cloudwith differing characteristics.

For example, in many organizations there’s a small, important group that requires ahigher service-level agreement than the majority of users. This is the so-called

“executive-floor server” scenario, in which IT wants to provide the most reliable andresponsive service to its most important users. In this case, IT provides these fewusers a private cloud, no-expense-spared service — compared with the perfectlyrespectable, yet low cost public-cloud service that 99.9% of users receive.

HYBRID CLOUD AND TEMPORARY SCALINGSome applications have vastly variable requirements at different times. This might bedue to unforeseen events — for example, a natural disaster causing a high rate ofinsurance claims. Or it could be a regular, planned-for event — for example, retailworkloads around Black Friday. But it can be difficult or expensive for a typical datacenter to cope with growth that’s fast, temporary or unexpected.

As we mentioned earlier, public clouds are inherently better at scaling up and down inresponse to demand. But what if your workload runs in your private cloud? In thatcase, it’s possible to temporarily augment it with public-cloud resources during thosepeak times. This is known as “cloudbursting” by some in the industry. iv,v

In our survey, IT managers showed a significant preference for public cloud when the

ability to quickly scale is important (39% of respondents).

HYBRID CLOUD IMPROVES UPTIMEHybrid cloud lets you avoid a single point of failure; it helps you recover fromdisasters and continue to run your business.

Many public clouds permit regional duplication in case of failure. And for the ultimatein reassurance, you can duplicate or distribute a workload across several separatecloud services. For example, Apple iCloud uses a hybrid mixture of its own privatecloud, plus at least three public clouds to ensure the highest level of service. vi

Hybrid cloud lets you avoid asingle point of

failure; it helps you recover fromdisasters andcontinue to run

your business.


10/13



Similarly, in case of disaster, a conventional on-premises application can betemporarily replaced by a public cloud. In simple terms, you create your owndisaster-recovery service by mirroring a private cloud instance to a standby publiccloud instance, or to another private cloud some distance away.

Attention to disaster-recovery and business-continuity reduces unplanned downtime,but what about planned downtime? The ability to upgrade and patch workloads whilethey continue running is an inherent advantage of a cloud architecture (althoughthere are other ways to achieve this in a non-cloud environment — e.g., sophisticatedstorage systems).

This is what some in the industry call immutability or phœnix servers . It’s animportant capability in “always on” environments. The beauty of this pattern is that itdoesn’t require the application to be designed to support online upgrading — legacy,monolithic workloads can be made highly available without modification.

Simplistically, it involves cloning or re-provisioning the running workload to beupgraded, performing the upgrade, replicating changes made during the upgradeprocess from the live instance to the new one, and then cutting over to the newinstance, with no noticeable service interruption. vii

In our survey, IT managers showed a significant belief that a private cloud is a goodplace to site a workload if reliability and uptime are important (41% of respondents).

HYBRID CLOUD ALLOWS HYBRID STORAGESome types of workloads might benefit from storing different types of data indifferent clouds. For example, Dropbox stores user files in a public cloud, but storesthe files’ metadata in its own data centers (although as noted earlier, Dropboxrecently repatriated most of the files, thanks to improved economies of scale).Enterprises have different needs when it comes to where data is stored. Some data isdeemed sensitive and companies prefer to store it on-premises, whereas some datais fit to store on cloud. Hybrid cloud data appliances can federate data and enablecompanies to manage which is stored on-premises and which in the cloud. This isimportant not only for corporate security, but also for information governancepolicies.

In addition, regulatory issues or legal restrictions might limit the location for storingand/or processing the data of some customers, but not others. For example, Boxplans to allow customers to choose where their files are stored, and on which cloudservice. The Zones feature allows its customers to choose a region and a public-cloudservice provider. The initial regions are Germany, Ireland, Singapore and Japan; theinitial cloud providers are IBM and AWS. viii

HOW TO DO HYBRID CLOUD A BRIEF OVERVIEW OF CLOUD TECHNOLOGY As we mentioned earlier, a true cloud is characterized by a specific technology, whichdifferentiates cloud from simple hosting or SaaS. That technology defines cloud, andit enables hybrid cloud.

Any cloud needs some way to package up the applications to be run in the cloudusing a technology known as virtualization . It lets the packaged workload run in yourown private cloud or in a shared, public cloud.

One of these packages can be run in a cloud environment, on any size of physicalhardware available in the cloud data center. Crucially, virtualization also allows thesepackages to share a physical machine, and to be moved between physical machines

— even between data centers — with essentially no interruption of service.

Virtualization also ensures the workload’s secure independence from other workloads,

Some types ofworkload mightbenefit fromstoring differenttypes of data indifferent clouds.


11/13



and it offers a management framework for controlling how the workload runs.

PLANNING IS CRITICAL As with many areas of IT and business, proper planning is crucial. While it’simpossible to fully predict the future, the reality of many data-center environments isone of fragile, legacy, “spaghetti” infrastructure. Such disjoint chaos can be difficultto unravel — not to mention expensive. That’s why it’s important to build a solidfoundation on which to grow your hybrid-cloud future.

The good news is there’s now a reasonably mature market of tools and services tohelp build your foundation. The early pioneers have already trodden the path,flattening down the major obstacles.

FOCUS ON FRAMEWORKS As well as the base-level virtualization technologies that enable hybrid cloud, werecommend choosing appropriate frameworks. These will help you manage yourworkloads, and help you move them between clouds.

For example, CNCF’s Kubernetes is an open-source container/cluster manager,developed out of Google’s internal production experience; and IBM PureApplicationsimplifies hybrid cloud by using reusable templates (“patterns”).

In addition, application, storage and database vendors are increasingly offeringframeworks to help federate, partition, migrate and mirror large, live data sets acrossclouds. For example, several popular cloud-storage architectures are based on theOpenStack framework.

Another important trend is in the use of standardized, all-in one, “datacenter-in-a-box” products, usually known as integrated or converged infrastructure. Productssuch as EMC VCE, Cisco/NetApp FlexPod, or IBM PureFlex promise to make it easierto build a private cloud, on-premises.

AVOID LOCK-INWe mentioned earlier that a hybrid cloud architecture allows you to avoid beinglocked in to a single public cloud service provider. The scenario to avoid is beingstuck on an under-performing or over-charging cloud.

When you approach IT from a hybrid cloud mentality, you naturally give yourself theoption to move a workload in the future. However, it’s important to fully understandyour cloud provider’s approach to its customers’ data.

This is a critical consideration, since there are varying levels of difficulty and expensewith which data can be retrieved from a cloud provider — such as when data needsto be moved to another service. If you wish to switch cloud providers, these types ofissues might unexpectedly hamper your move, not to mention the potential forregulatory compliance failure.

Another important part of avoiding lock-in is to ensure your service providers supportopen APIs. Indeed, your providers shouldn’t merely pay lip service to openness, butsupport open APIs as a first-class feature. You should also clearly determine andspecify who manages what as a service: Infrastructure, platforms, data andapplications can all be managed by some cloud providers.

THE PSYCHOLOGY OF TERMINOLOGYBut IT managers shouldn’t underestimate the potential for confusion or inflatedexpectations among peers and internal, line-of-business customers. Confusion canarise thanks to the varied understanding of the word “cloud” — it can mean differentthings to different people. So, take care not to make assumptions about youraudience’s level of knowledge.

When youapproach IT

from a hybridcloud mentality,

you naturally give yourself theoption to move a

workload in the future.


12/13



Similarly, by recasting existing, internal IT capability as “private cloud,” you risksetting unrealistic expectations. When referring to legacy workloads as “cloud”, takecare, lest your audience compares your performance against consumer cloudservices.

In our survey, the respondents were split when asked about service performance ofpublic vs. private cloud, with no significant trend of opinion.THE BAD NEWS: THE LAWS OF PHYSICS

And finally, no discussion of cloud would be complete without a realistic recognitionof physical limitations. With some types of workloads, interactive responsiveness iscritical to user satisfaction. However, the speed of light imposes an absolute limit onhow quickly a server can respond — a phenomenon known as latency . In essence,the further away from the user a cloud service is, the poorer the perceived quality ofthe application.

Moving a workload from an on-premises data center to a remote cloud might addunacceptable latency. This could make your choice of cloud service provider morecomplex for responsiveness-critical applications. Also, the bulk data transfer speedbetween a user and a public cloud service is likely to be worse than with an on-premises data center.

Similarly, when considering the migration of a workload between clouds, you should

think carefully about how much bandwidth is available to transfer the virtualizedworkload and/or its data, and how the use of that bandwidth is charged. As wementioned earlier, different service providers use different accounting models fordata transfer.

Internet speeds have improved immeasurably since he said it in 1981, but Professor Andrew S. Tanenbaum’s classic computer-science moral still holds true:

Never underestimate the bandwidth of a station wagon full of tapeshurtling down the highway. ix

SUMMARYCloud architectural techniques offer huge value when used in your own data center.Plus, they permit you to easily move and share workloads between your data centerand public cloud services.

The benefits are clear: Hybrid cloud allows you to save money, while meetingbusiness and regulatory needs. And early adopters have already flattened thepathways for you.

However, there’s the danger of terminology confusion within the organization. Andhybrid cloud isn’t a magic wand that can fix a badly planned or poorly performingapplication.

Nevertheless, the shift to hybrid cloud is all-but inevitable, so grasp the opportunity.


13/13



SPONSOR OF THIS WHITE PAPERStorage Made Easy provides an Enterprise File Share and Sync Fabric that enables ITto regain control of “data sprawl", unifying private and public file sharing intoa single, converged storage infrastructure that can easily be managed and be used toset governance and audit controls.

The SME solution offers a “blanket” that enterprises can privately apply to wraparound all their data, whether object storage or file or block storage, and whether on-

premises, within a public cloud, or on a third party software vendors’ cloud(SharePoint or SalesForce for example). Customers use SME to provide a federatedhybrid cloud in addition to providing unified security, encryption, audit, and control.

Storage Made Easy is the trading name of Vehera LTD who have sales offices in theUK, USA and Switzerland.

© 2016 Osterman Research, Inc. All rights reserved.

No part of this document may be reproduced in any form by any means, nor may it bedistributed without the permission of Osterman Research, Inc., nor may it be resold ordistributed by any entity other than Osterman Research, Inc., without prior written authorizationof Osterman Research, Inc.

Osterman Research, Inc. does not provide legal advice. Nothing in this document constituteslegal advice, nor shall this document or any software product or other offering referenced hereinserve as a substitute for the reader’s compliance with any laws (including but not limited to anyact, statute, regulation, rule, directive, administrative order, executive order, etc. (collectively,

“Laws”)) referenced in this document. If necessary, the reader should consult with competentlegal counsel regarding any Laws referenced herein. Osterman Research, Inc. makes norepresentation or warranty regarding the completeness or accuracy of the information containedin this document.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS ORIMPLIED REPRESENTATIONS, CONDITIONS AND WARRANTIES, INCLUDING ANY IMPLIEDWARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AREDISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE DETERMINED TO BEILLEGAL.

REFERENCES i blog.softlayer.com/tag/definition (one attempt to define “public” and “private” cloud)ii dincloud.com/blog/what-are- the-many-types-of-cloud (another attempt)iii www.richi.uk/cwa/3044261 (author’s roundup of Dropbox hybrid-cloud news)iv intel.ie/content/www/ie/en/cloud-computing/cloud-bursting-infographic.html (cloudbursting)v youtu.be/pllRW9wETzw (not to be confused with cloudbusting)vi www.richi.uk/cwa/3045439 (author’s roundup of Apple hybrid-cloud news)vii chadfowler.com/2013/06/23/immutable-deployments.html (immutability)viii www.box.com/blog/introducing-box-zones (Box Zones example)ix Tanenbaum and Wetherall, Computer Networks , 5 th ed., Pearson, 2011, sec. 2.2.1

www.storagemadeeasy.com

@SMEStorage

Skype: storagemadeeasy

[email protected]

Documents

The What, The Why, And the How of Hybrid Cloud - SME