Issue link: https://insights.oneneck.com/i/1200933
Chapter 7: Enabling Hybrid IT 53 These materials are © 2017 John Wiley & Sons, Inc. Any dissemination, distribution, or unauthorized use is strictly prohibited. The major downside is one that you simply can't get around, and that's the cost of getting out. That outbound data transfer is a fee that you won't incur until you try to leave, so make sure you plan appropriately if you decide to exit. Enabling workload transparency When you're running services on‐premises, it can be easy to think of them as "free" because you own the hardware. With the cloud, you see the specific charges for each and every workload and, in general, providers can tell you up front about what kind of pricing you should expect to see. In this way, you may actually have more financial control over your workloads when they're running in the cloud rather than on‐premises. Of course, if you have a huge sunk cost in infrastructure, the additive cost of a new workload is pretty close to free in a lot of cases, as least from an infrastructure perspective, but you don't have as much insight into what resources that workload may be consuming. The perception of control "The cloud provider is down and I feel helpless." This is some- times cited as one of the challenges in cloud adoption. There is a feeling of helplessness when a provider goes down. If you have a local outage, your team can spring into action. There is a higher degree of control when workloads run on‐premises. In addition, cloud sprawl can become a security and compli- ance nightmare thanks to rogue business departments — sometimes referred to as shadow IT. For example, it's very easy to add credit cards to a cloud provider and standup workloads and have no thought to security, compliance, or data sovereignty. Such scenarios can also lead to cloud sprawl with no optimization at all, as one group does not know what the next is doing.