Welcome!

Microservices Expo Authors: Elizabeth White, Pat Romanski, Liz McMillan, Harry Trott, Mamoon Yunus

Related Topics: @CloudExpo, Java IoT, Microservices Expo, Linux Containers, @BigDataExpo, SDN Journal

@CloudExpo: Article

What’s Missing from “Cloud First” in the Enterprise?

Cloud First doesn’t just apply to applications, it needs to apply to infrastructure as well

My first experience with an "inverted yield curve" was in 2000 just prior to the tech bubble bursting. I was working on a financial portal for an investment bank and one of the charts was a yield curve. It looked odd all of a sudden, so I looked it up in a book of financial terms. An inverted yield is indicated when interest rates for short-term capital are higher than interest rates for long-term capital. In other words, people are willing to pay a significant price to alleviate short-term concerns because they're focused on the now and not so concerned about one year, three years, five years, or thirty years from now. Inverted yield curves some believe signal disruption in financial markets. On the surface, Cloud First seems to signal the disruption that is cloud computing. To take this metaphor a little further, this inversion of Cloud First from "Cloud Never" suggests to me an inverted set of concerns. Does Cloud First prioritize an immediate need to say "something" about the cloud and cloud strategy? Does Cloud First prioritize the now while discounting near, mid, and long-term opportunities that far exceed the "costs less, more agile, faster time-to-market" recording I hear played daily throughout the blogosphere? Beyond saying "Cloud First!" what else can enterprise technology teams prioritize that may amplify their ability to execute in the cloud?

One of the primary strengths of "Cloud First" is the simplicity:

Q: "Hey, where do we deploy the new financial system?"

A: "Put it in the cloud."

Yet the real power of Cloud First lies in the underlying recognition that details and choices, as they filter down through multiple levels of management, quickly become confusing. On many levels in corporate IT I get the sense that the more details provided, the more likely things will go forth along an unintended arc.

Cloud First reminds me of the trailer from the movie "Face Off" starring Nicholas Cage and John Travolta, in which they actually do trade faces for a while. The best thing about the title of the movie is that you know something pretty amazing (and possibly horrifying) is going to happen and it grabs your attention. Cloud First? - same thing - it's got everyone's attention: we're unleashing the monster the media has been warning you about and it's too late to turn back. If we need to do a sequel we'll call it "Mobile First."

What Does Cloud First Look Like?
What Cloud First lacks that the movie title "Face Off" owns is the power to place a clear mental image in the mind of its audience. In a Cloud First organization where I worked, to give meaning to the mantra, I invited guest speakers from successful cloud startups to present their business and talk about cloud. One of my favorite speakers was Stephane Dubois, CEO of Xignite, a cloud market data service that serves billions of requests per month. Xignite's business model of serving data to the underserved "long tail" of the market as well as creating a network effect that multiplies the value of the data in the cloud demonstrates opportunities executives need to keep in sharp focus and track closely. In this way Xignite is a great technology example in a "relatable" industry that values uptime. By bringing in business leaders to present what they're doing in a "serious" business, CIOs and business leaders can build a vision of what success in the cloud might look like for their business.

What Does Cloud First Lack?
What Cloud First lacks in specificity of mission, it also lacks in implementation guidelines. This lack of specific guidelines could be a strength. Or, if you play with the words a little you might work out that Cloud First means "consume cloud services first," and never build or drag data center technology across a VPN or otherwise contaminate the cloud with infrastructure crushed under the weight of the interest on 20 or more years of accumulated technical debt. But since nobody I've met in corporate IT seems to arrive at that interpretation of Cloud First organically, I've provided some guidelines.

Whatever cloud you're on, try to consume cloud services. As an architect, specifying services rather than asking teams brand new to cloud to quickly build robust, highly available databases that will withstand the rolling outages of a year like 2012 is really unfair, and it just won't happen. It's like the scene in "Kill Bill" where the "Crazy 88" suddenly demand 20 pizzas in a Sushi restaurant. It will just exasperate people and make them go, well, crazy. In cases where an Oracle RAC database was absolutely necessary I solved the problem by defining an architecture in which the application layer ran in the cloud, but the database ran "close" to the cloud via a low latency fiber cross-connect. I don't suggest you try this unless there's no other option, as was the case in 2011 when I worked on that solution.

In other words, it's really difficult for IT teams in large corporations to suddenly build highly available databases in the cloud. I've seen it end very badly even when implemented by good people. In many cases the services available in the cloud have the scalability and availability "wrapped" into the service. Similar to the way Linux succeeded largely because "with enough eyes all bugs are shallow," perhaps the cloud manifesto is that given enough implementations and users, a cloud services performance and availability will blow away a one-off, bespoke database implementation built by a team new to cloud. Not building services from scratch may not be as much fun or as hard core as what the cool startups do, but you'll have plenty of interesting things to figure out without building everything from the ground up. One of the rules of Cloud First is to focus your team's energy and avoid fighting battles on soggy unfamiliar ground. One of the more subtle messages of Cloud First is that a key element of a corporate cloud strategy is to avoid building stuff from scratch unless you have zero other options. People may work very hard to convince you to do otherwise, but stick to cloud services first.

Cloud First Doesn't Just Apply to Applications. It Needs to Apply to Infrastructure as Well
The cloud seems to be all about application developers. Yet corporate IT could be more Cloud First focused. I just don't see enough IT organizations following Cloud First when it comes to DNS services, storage services for offsite data backup, content distribution, or disaster recovery. Some CIOs really do follow a Cloud First strategy and make it meaningful. For example, one of my forward-thinking CIO customers first asked his team how they could leverage cloud storage to replace an ailing file server. (No Nirvanix jokes please.)

More Stories By Brian McCallion

Brian McCallion Bronze Drum works with executives to develop Cloud Strategy, Big Data proof-of-concepts, and trains enterprise teams to rethink process and operations. Focus areas include: Enterprise Cloud Strategy and Project Management Cloud Data Governance and Compliance Infrastructure Automation

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
While some vendors scramble to create and sell you a fancy solution for monitoring your spanking new Amazon Lambdas, hear how you can do it on the cheap using just built-in Java APIs yourself. By exploiting a little-known fact that Lambdas aren’t exactly single-threaded, you can effectively identify hot spots in your serverless code. In his session at @DevOpsSummit at 21st Cloud Expo, Dave Martin, Product owner at CA Technologies, will give a live demonstration and code walkthrough, showing how ...
Did you know that you can develop for mainframes in Java? Or that the testing and deployment can be automated across mobile to mainframe? In his session and demo at @DevOpsSummit at 21st Cloud Expo, Dana Boudreau, a Senior Director at CA Technologies, will discuss how increasingly teams are developing with agile methodologies, using modern development environments, and automating testing and deployments, mobile to mainframe.
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory?
@DevOpsSummit at Cloud Expo taking place Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center, Santa Clara, CA, is co-located with the 21st International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is ...
With Cloud Foundry you can easily deploy and use apps utilizing websocket technology, but not everybody realizes that scaling them out is not that trivial. In his session at 21st Cloud Expo, Roman Swoszowski, CTO and VP, Cloud Foundry Services, at Grape Up, will show you an example of how to deal with this issue. He will demonstrate a cloud-native Spring Boot app running in Cloud Foundry and communicating with clients over websocket protocol that can be easily scaled horizontally and coordinate...
Most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes a lot of work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reduction in cost ...
There are several reasons why businesses migrate their operations to the cloud. Scalability and price are among the most important factors determining this transition. Unlike legacy systems, cloud based businesses can scale on demand. The database and applications in the cloud are not rendered simply from one server located in your headquarters, but is instead distributed across several servers across the world. Such CDNs also bring about greater control in times of uncertainty. A database hack ...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
DevOps at Cloud Expo, taking place October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 21st Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to w...
API Security is complex! Vendors like Forum Systems, IBM, CA and Axway have invested almost 2 decades of engineering effort and significant capital in building API Security stacks to lockdown APIs. The API Security stack diagram shown below is a building block for rapidly locking down APIs. The four fundamental pillars of API Security - SSL, Identity, Content Validation and deployment architecture - are discussed in detail below.
IT organizations are moving to the cloud in hopes to approve efficiency, increase agility and save money. Migrating workloads might seem like a simple task, but what many businesses don’t realize is that application migration criteria differs across organizations, making it difficult for architects to arrive at an accurate TCO number. In his session at 21st Cloud Expo, Joe Kinsella, CTO of CloudHealth Technologies, will offer a systematic approach to understanding the TCO of a cloud application...
API Security has finally entered our security zeitgeist. OWASP Top 10 2017 - RC1 recognized API Security as a first class citizen by adding it as number 10, or A-10 on its list of web application vulnerabilities. We believe this is just the start. The attack surface area offered by API is orders or magnitude larger than any other attack surface area. Consider the fact the APIs expose cloud services, internal databases, application and even legacy mainframes over the internet. What could go wrong...
Cloud adoption is often driven by a desire to increase efficiency, boost agility and save money. All too often, however, the reality involves unpredictable cost spikes and lack of oversight due to resource limitations. In his session at 20th Cloud Expo, Joe Kinsella, CTO and Founder of CloudHealth Technologies, tackled the question: “How do you build a fully optimized cloud?” He will examine: Why TCO is critical to achieving cloud success – and why attendees should be thinking holistically ab...
Web services have taken the development world by storm, especially in recent years as they've become more and more widely adopted. There are naturally many reasons for this, but first, let's understand what exactly a web service is. The World Wide Web Consortium (W3C) defines "web of services" as "message-based design frequently found on the Web and in enterprise software". Basically, a web service is a method of sending a message between two devices through a network. In practical terms, this ...
Docker is on a roll. In the last few years, this container management service has become immensely popular in development, especially given the great fit with agile-based projects and continuous delivery. In this article, I want to take a brief look at how you can use Docker to accelerate and streamline the software development lifecycle (SDLC) process.
The goal of Continuous Testing is to shift testing left to find defects earlier and release software faster. This can be achieved by integrating a set of open source functional and performance testing tools in the early stages of your software delivery lifecycle. There is one process that binds all application delivery stages together into one well-orchestrated machine: Continuous Testing. Continuous Testing is the conveyer belt between the Software Factory and production stages. Artifacts are m...
We define Hybrid IT as a management approach in which organizations create a workload-centric and value-driven integrated technology stack that may include legacy infrastructure, web-scale architectures, private cloud implementations along with public cloud platforms ranging from Infrastructure-as-a-Service to Software-as-a-Service.
In his session at @DevOpsSummit at 20th Cloud Expo, Kelly Looney, director of DevOps consulting for Skytap, showed how an incremental approach to introducing containers into complex, distributed applications results in modernization with less risk and more reward. He also shared the story of how Skytap used Docker to get out of the business of managing infrastructure, and into the business of delivering innovation and business value. Attendees learned how up-front planning allows for a clean sep...
In IT, we sometimes coin terms for things before we know exactly what they are and how they’ll be used. The resulting terms may capture a common set of aspirations and goals – as “cloud” did broadly for on-demand, self-service, and flexible computing. But such a term can also lump together diverse and even competing practices, technologies, and priorities to the point where important distinctions are glossed over and lost.
Enterprise architects are increasingly adopting multi-cloud strategies as they seek to utilize existing data center assets, leverage the advantages of cloud computing and avoid cloud vendor lock-in. This requires a globally aware traffic management strategy that can monitor infrastructure health across data centers and end-user experience globally, while responding to control changes and system specification at the speed of today’s DevOps teams. In his session at 20th Cloud Expo, Josh Gray, Chie...