eBooks

OreillyMultiCloudFinalEBOOK

Learn all you need to know about email best practices, deliverability, and tools with email whitepapers and ebooks.

Issue link: https://hub.dyn.com/i/1119883

Contents of this Issue

Navigation

Page 18 of 57

But there is a difference between moving to the cloud and moving to a multicloud or hybrid cloud environment. Let's take a closer look at how to evaluate which strategy is right for your organization. Weighing the Pros and Cons As with any business decision, it is important to look at the big pic‐ ture, ignore the hype, and weigh the pros and cons of moving to a multicloud environment. You can begin by examining where the application sits now. Is it hosted in a datacenter managed by your organization, colocated, or is it already hosted in a cloud provider's datacenter? Making the jump from a locally hosted application to one that is hosted in mul‐ tiple datacenters around the world might be too much of a jump (not always, but for many organizations it is). Most organizations start by moving their application to a single cloud provider first. This allows the organization to better understand the experience and the challenges associated with cloud migration. For example, the organization might find that its application code is not as portable as it once thought. After you have experience working in a cloud environment, the jump to a multicloud architecture is easier. (Note: We didn't say that it will be easy, just easier.) It's also important to determine how much control your team is will‐ ing to surrender to the cloud providers. Cloud providers offer a range of services from the most basic, in which the cloud provider simply offers hardware and a range of IP addresses, all the way up to a fully managed service. The service you choose is also a budgetary matter. The more cloud provider services you take advantage of, the greater the costs. And of course, all of this has to synchronize across multiple provid‐ ers. For example, in a fully managed cloud environment, it's impor‐ tant to know how quickly your provider installs patches. You don't want to have half of your servers vulnerable to an exploit weeks after a patch is released, or have systems stop working because the code depends on a specific library that has been updated on one provider but not another. It is important to fully document code and dependencies prior to moving to a multicloud environment—and you must demand the same from your cloud providers. You need to fully understand the services the organization is using, what the cloud providers' patch‐ Evaluation | 13

Articles in this issue

view archives of eBooks - OreillyMultiCloudFinalEBOOK