Most Read This Week
From the Blogosphere
How to Avoid Cloud Fatigue | @CloudExpo #CloudNative #Serverless #AI #DX
Companies that successfully deploy public cloud platforms have brought together the right blend of cloud & technical expertise
By: Greg Pierce
Jan. 31, 2018 02:45 PM
Understanding Cloud Complexities and Avoiding "Cloud Fatigue"
We're seeing an emerging trend in the cloud computing world. I've been referring to it as cloud fatigue, but it's more commonly known as repatriation, or moving workloads from the cloud back to on-prem locations. According to a recent 451 Research report, over 21 percent of organizations have plans to pull back from the cloud and return to an on-prem infrastructure in 2017. Considering the vast growth of cloud adoption over the last several years, what's behind this trend?
We believe cloud fatigue is the result of deployments going awry. It usually happens when companies quickly adopt one of the leading public cloud platforms (Amazon Web Services, Microsoft Azure, etc.) because they're attracted to the promises of ease-of-use, flexibility and low computing costs. What happens next depends on a myriad of factors, including the technical depth an organization has in-house or the partner network it has in place, as well as a strategic plan for digital transformation.
The companies that successfully deploy these public cloud platforms have typically brought together the right blend of internal and external cloud and technical expertise. But, increasingly, we're hearing about situations where the promise of the public cloud has failed to come true, or costly disruptions occur (e.g., last year's AWS outage that affected Netflix, Tinder and other well-known organizations). To provide further clarity, below are two fictional scenarios that illustrate this growing occurrence.
Scenario #1: Astronomical Consumption Costs
The reason for the soaring costs? A lack of internal expertise to configure and manage the company's public cloud environment in a way to keep performance high and costs consistent. Choosing the right service, applications and features can be overwhelming. And interfacing with a computer screen instead of a human, which is the norm for public cloud providers, doesn't help the process. The complexity was underestimated.
The company considered shifting its cloud infrastructure to on-prem, but decided it needed a consultant before moving forward. Executives enlisted a cloud services provider that rewired the cloud configuration to eliminate unnecessary instances and server sprawl. Eventually, the company's costs were reduced by half and became more predictable.
Scenario #2: Poor Performance and Reliability Issues
With the help of a cloud services provider it is determined the servers had been misconfigured - a kind of "worst practice" scenario. The team ends up configuring a hybrid solution that combines the public cloud's scale and power with the security and compliance capabilities of a private cloud platform. The company's healthcare ERP now works flawlessly.
Reader Feedback: Page 1 of 1
Subscribe to the World's Most Powerful Newsletters
Today's Top Reads