Welcome!

Microservices Expo Authors: Flint Brenton, Automic Blog, AppDynamics Blog, Liz McMillan, Sujoy Sen

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
As the software delivery industry continues to evolve and mature, the challenge of managing the growing list of the tools and processes becomes more daunting every day. Today, Application Lifecycle Management (ALM) platforms are proving most valuable by providing the governance, management and coordination for every stage of development, deployment and release. Recently, I spoke with Madison Moore at SD Times about the changing market and where ALM is headed.
From the conception of Docker containers to the unfolding microservices revolution we see today, here is a brief history of what I like to call 'containerology'. In 2013, we were solidly in the monolithic application era. I had noticed that a growing amount of effort was going into deploying and configuring applications. As applications had grown in complexity and interdependency over the years, the effort to install and configure them was becoming significant. But the road did not end with a ...
The goal of any tech business worth its salt is to provide the best product or service to its clients in the most efficient and cost-effective way possible. This is just as true in the development of software products as it is in other product design services. Microservices, an app architecture style that leans mostly on independent, self-contained programs, are quickly becoming the new norm, so to speak. With this change comes a declining reliance on older SOAs like COBRA, a push toward more s...
Small teams are more effective. The general agreement is that anything from 5 to 12 is the 'right' small. But of course small teams will also have 'small' throughput - relatively speaking. So if your demand is X and the throughput of a small team is X/10, you probably need 10 teams to meet that demand. But more teams also mean more effort to coordinate and align their efforts in the same direction. So, the challenge is how to harness the power of small teams and yet orchestrate multiples of them...
Many private cloud projects were built to deliver self-service access to development and test resources. While those clouds delivered faster access to resources, they lacked visibility, control and security needed for production deployments. In their session at 18th Cloud Expo, Steve Anderson, Product Manager at BMC Software, and Rick Lefort, Principal Technical Marketing Consultant at BMC Software, will discuss how a cloud designed for production operations not only helps accelerate developer...
In a crowded world of popular computer languages, platforms and ecosystems, Node.js is one of the hottest. According to w3techs.com, Node.js usage has gone up 241 percent in the last year alone. Retailers have taken notice and are implementing it on many levels. I am going to share the basics of Node.js, and discuss why retailers are using it to reduce page load times and improve server efficiency. I’ll talk about similar developments such as Docker and microservices, and look at several compani...
SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical. In his session at @DevOpsSummit at 18th Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningfu...
In the world of DevOps there are ‘known good practices’ – aka ‘patterns’ – and ‘known bad practices’ – aka ‘anti-patterns.' Many of these patterns and anti-patterns have been developed from real world experience, especially by the early adopters of DevOps theory; but many are more feasible in theory than in practice, especially for more recent entrants to the DevOps scene. In this power panel at @DevOpsSummit at 18th Cloud Expo, moderated by DevOps Conference Chair Andi Mann, panelists will dis...
Last week I had the pleasure of speaking on a panel at Sapphire Ventures Next-Gen Tech Stack Forum in San Francisco. Obviously, I was excited to join the discussion, but as a participant the event crystallized not only where the larger software development market is relative to microservices, container technologies (like Docker), continuous integration and deployment; but also provided insight into where DevOps is heading in the coming years.
Wow, if you ever wanted to learn about Rugged DevOps (some call it DevSecOps), sit down for a spell with Shannon Lietz, Ian Allison and Scott Kennedy from Intuit. We discussed a number of important topics including internal war games, culture hacking, gamification of Rugged DevOps and starting as a small team. There are 100 gold nuggets in this conversation for novices and experts alike.
The notion of customer journeys, of course, are central to the digital marketer’s playbook. Clearly, enterprises should focus their digital efforts on such journeys, as they represent customer interactions over time. But making customer journeys the centerpiece of the enterprise architecture, however, leaves more questions than answers. The challenge arises when EAs consider the context of the customer journey in the overall architecture as well as the architectural elements that make up each...
Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important – because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators. But new code doesn’t just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performan...
Admittedly, two years ago I was a bulk contributor to the DevOps noise with conversations rooted in the movement around culture, principles, and goals. And while all of these elements of DevOps environments are important, I’ve found that the biggest challenge now is a lack of understanding as to why DevOps is beneficial. It’s getting the wheels going, or just taking the next step. The best way to start on the road to change is to take a look at the companies that have already made great headway ...
In 2006, Martin Fowler posted his now famous essay on Continuous Integration. Looking back, what seemed revolutionary, radical or just plain crazy is now common, pedestrian and "just what you do." I love it. Back then, building and releasing software was a real pain. Integration was something you did at the end, after code complete, and we didn't know how long it would take. Some people may recall how we, as an industry, spent a massive amount of time integrating code from one team with another...
I have an article in the recently released “DZone Guide to Building and Deploying Applications on the Cloud” entitled “Fullstack Engineering in the Age of Hybrid Cloud”. In this article I discuss the need and skills of a Fullstack Engineer with relation to troubleshooting and repairing complex, distributed hybrid cloud applications. My recent experiences with troubleshooting issues with my Docker WordPress container only reinforce the details I wrote about in this piece. Without my comprehensive...
Struggling to keep up with increasing application demand? Learn how Platform as a Service (PaaS) can streamline application development processes and make resource management easy.
If there is anything we have learned by now, is that every business paves their own unique path for releasing software- every pipeline, implementation and practices are a bit different, and DevOps comes in all shapes and sizes. Software delivery practices are often comprised of set of several complementing (or even competing) methodologies – such as leveraging Agile, DevOps and even a mix of ITIL, to create the combination that’s most suitable for your organization and that maximize your busines...
Digital means customer preferences and behavior are driving enterprise technology decisions to be sure, but let’s not forget our employees. After all, when we say customer, we mean customer writ large, including partners, supply chain participants, and yes, those salaried denizens whose daily labor forms the cornerstone of the enterprise. While your customers bask in the warm rays of your digital efforts, are your employees toiling away in the dark recesses of your enterprise, pecking data into...
You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.