This is important to consider...if you go talk to a major cloud provider, of course they are going to show you how they can solve for world peace and hunger while saving you money, right?
My favorite of these conceptions is that cloud is cheaper on a per unit cost basis. In the vast majority of cases, this is simply not true. At our day jobs, we do detailed analysis on a workload by workload basis of applications and find that the vast majority of workloads are more expensive to operate in a public cloud. Yes, more expensive. So why deploy to a public cloud? Opportunity cost.
Today's business marketplace is finding startups are coming in and disrupting the core businesses of several industries. We refer to them "*-techs", with some examples being fintechs (financial services disruptors), healthtechs (health insurance disruptors), markettechs (retail disruptors), or edutechs (education disruptors). In each case, these "plays" find something they can do much more efficiently than the legacy leaders in that business and work to disrupt and displace the entrenched leaders in that space. A perfect example is a company who can do "wire transfers" more efficiently and/or cheaper than a traditional bank or financial services firm. Rather than trying to attack the leader by taking them head on, they simply go after one element of that business. While this sounds fairly innocuous, now imagine that you are one of the top 50 traditional banks and instead of having to deal with one disruptor in wire transfers, you have 40-50 different ones each attacking you in different areas. Scary...
This is where things get tricky. Other than buying the disruptor out of the marketplace, the "-tech" can typically outperform a traditional business because their code is written in a manner that allows new business functionality to be released very rapidly. An example of this is facebook, where they can release new functionality multiple times a day. This is due to embracing an architectural model around "Microservices," the concept of decoupling large complex applications into much smaller functions that are built around Application Programmable Interfaces (API). The concept of APIs are well documented in other places on the internet, however what is the key to our story is that in a microservices architecture, APIs enable functionality to be deployed rapidly. Why? If I can decouple a single function into a standalone service with a pre-defined language and structure for requests coming in and going out, then I can change the function in the middle as necessary as often as I would like as long as the API inputs and outputs remain the same.
Compared to monolithic applications, this allows new functionality to be released as soon as it is available, rather than waiting for the next release. And every traditional enterprise in the entrenched leader category has to release against a monolithic paradigm (unless they have upgraded to microservices). Which, consequently, we are seeing a massive effort to refactor monolithic applications into a microservices framework as fast as possible.
And this is where public cloud platforms shine. If you ask internal IT to develop a new development platform to support rapid application development and refactoring to microservices, it would take a smart IT organization a minimum of 9-18 months to bring the platform online after all of the standards are established, agreed upon in triplicate, socialized, revised, and then built from scratch. Only then can you start functionality development...By then you have given that "-tech" disruptor an insurmountable lead.
Or you can give Amazon, Azure, Google, or Rackspace a credit card and use their platforms ready...right now. So while the unit cost is higher, the opportunity cost makes the speed of cloud a necessity...especially when you are playing defense against a disruptor who has a more efficient way to do an element of your business.
Actually no. The rise of the hybrid data center is really to address the discrepancy between new and traditional forms of IT applications. Gartner refers to this as "Bi-Modal". Forrester refers to this disparity as "multi-modal". Cloud Developers speak in terms of Agile DevOps and Waterfall. In the end, they are all saying the same thing. Some applications need to pay the premium to enable a rapid rate of change. Others simply don't need it and therefore do not require the premium. How to tell which will be a topic for a different blog.
Cloud is not easier, nor is it a silver bullet. But it can solve several problems that IT is not ready to solve. At the end of the day, IT has embraced the cloud because if they cannot keep pace, developers working for the business have demonstrated that they will seek solutions outside of IT.
In other blog posts, we will tackle questions like migrating applications to the cloud, understanding how not to break applications in the process, building and designing IT solutions around cloud capabilities, bridging private and public to balance speed vs. unit cost, and helping IT focus on how to disrupt itself to improve its role in the enterprise.
Sit down and buckle up. We are in a chaotic and confusing time in IT, however, the opportunity has never been better to make a difference.