@CloudExpo Authors: Yeshim Deniz, Liz McMillan, Pat Romanski, Zakia Bouachraoui, Carmen Gonzalez

Related Topics: @CloudExpo, Microservices Expo, Containers Expo Blog

@CloudExpo: Blog Post

Sorting Through the Cloud Jargon

Looking at five overloaded pieces of cloud jargon

Over the last two weeks, I have fully immersed myself in the world of cloud. Thanks to conference keynotes, breakout sessions, customer briefings, and ad hoc discussions, I have not had much time to not think or talk about cloud. While this is not necessarily a bad thing, I do have to admit, something has been gnawing at me over these past two weeks: There is too much overloaded, confusing, or misunderstood cloud jargon.

The thing is, just about everyone in the cloud space is guilty of misuse at one point in time (I know I make my contributions). However, it is good to cast a light on some of this behavior in hopes that we can fix it and prevent the consumer confusion it can sometimes cause. Therefore, because I want to pitch in and do my part to help correct this behavior, and because lists are fun to make, here is my opinion on the top five overloaded/confusion-causing terms in the cloud space today:

- Service: I am not sure there is any term more used, yet less specific than the term service. I suspect this is the case regardless of what technological context the term ‘service' comes up in, but I know it for a fact when used in the context of cloud discussions.  In cloud computing, services can be servers, storage, networking, business processes, application platforms, applications, and much more. In my view, it is certainly fine to position your cloud computing solution as helping users quickly deliver services. The only problem I have is when you say that but do not bother disambiguating what you mean by service. Tell us exactly what ‘services' you are delivering.

- Dynamic: Ask yourself this: Is there anything that is not dynamic when it comes to the cloud? The term has a variety of meanings ranging from autonomic behavior to elasticity of resources. I use the term dynamic from time-to-time, and in many cases, consumers call me on the carpet and ask exactly what I mean. That is fair and is in fact the right thing for them to do due to the overuse and frankly, abuse of the term. I hope that providers are using the term where appropriate and they are ready to explain exactly what they mean by ‘dynamic'.

- Workload: Like ‘service', the term ‘workload' is not at all specific in the context of cloud, but it comes up all the time. Unlike ‘dynamic', I don't see a lot of misuse of this term, but confusion ensues because of one primary reason. The meaning of workload is highly dependent on who you are talking to within an organization. As an example, to an application platform administrator, provisioning a new application platform may be a workload. However, for a developer that deploys applications to that platform, their definition of workload probably involves application requests. Help everyone out here. When you talk about workloads within a cloud computing solution, start by defining the workload.

- Virtualization: The confusion I typically observe in this space results from the fact that when users hear ‘virtualization' they usually think hypervisors and virtual machines. In fact, the concept of virtualization is simply a logical abstraction of a discrete set of resources. Cloud solutions today apply virtualization at the server level, application infrastructure level, and even the application level to name but a few. Like with many of the terms mentioned above, when using ‘virtualization' or ‘virtualized', don't just use it as a sweeping generalization. Be specific. Tell us exactly what you are virtualizing and what that means to the end user.

- Hybrid cloud: While there is constant bickering about public and private clouds, many seemingly agree that hybrid clouds are the eventuality of many cloud architectures. The problem is, we overload, and in my opinion, often misuse the term ‘hybrid cloud'. To me, a hybrid cloud architecture is one consisting of both private and public clouds. Connecting your traditionally deployed on-premise application environments with cloud-based environments in the public realm is extremely valuable, but I cannot bring myself to call that a hybrid cloud. Hybrid architecture, sure, but not a hybrid cloud. I think the difference here is important because hybrid clouds and hybrid architectures dictate different usage scenarios. We need to be consistent and accurate when using the term ‘hybrid cloud'.

This is my list of overloaded and sometimes misunderstood terms in the cloud. What do you think?

More Stories By Dustin Amrhein

Dustin Amrhein joined IBM as a member of the development team for WebSphere Application Server. While in that position, he worked on the development of Web services infrastructure and Web services programming models. In his current role, Dustin is a technical specialist for cloud, mobile, and data grid technology in IBM's WebSphere portfolio. He blogs at http://dustinamrhein.ulitzer.com. You can follow him on Twitter at http://twitter.com/damrhein.

CloudEXPO Stories
Big Switch's mission is to disrupt the status quo of networking with order of magnitude improvements in network e ciency, intelligence and agility by delivering Next-Generation Data Center Networking. We enable data center transformation and accelerate business velocity by delivering a responsive, automated, and programmable software-dened networking (SDN) fabric-based networking solution. Traditionally, the network has been viewed as the barrier to data center transformation as legacy networking architectures hinder IT organizations with brittle, complex and cumbersome switch-by-switch management paradigms and in exible, proprietary hardware choices that are increasingly unable to keep up with the pace required of businesses today.
Lori MacVittie is a subject matter expert on emerging technology responsible for outbound evangelism across F5's entire product suite. MacVittie has extensive development and technical architecture experience in both high-tech and enterprise organizations, in addition to network and systems administration expertise. Prior to joining F5, MacVittie was an award-winning technology editor at Network Computing Magazine where she evaluated and tested application-focused technologies including app security and encryption-related solutions. She holds a B.S. in Information and Computing Science from the University of Wisconsin at Green Bay, and an M.S. in Computer Science from Nova Southeastern University, and is an O'Reilly author.
Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term. A total of 88% of Fortune 500 companies from a generation ago are now out of business. Only 12% still survive. Similar percentages are found throughout enterprises of all sizes. We are offering early bird savings on all ticket types where you can save significant amount of money by purchasing your conference tickets today.
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker containers gain prominence. He explored these challenges and how to address them, while considering how containers will influence the direction of cloud computing.
Daniel Jones is CTO of EngineerBetter, helping enterprises deliver value faster. Previously he was an IT consultant, indie video games developer, head of web development in the finance sector, and an award-winning martial artist. Continuous Delivery makes it possible to exploit findings of cognitive psychology and neuroscience to increase the productivity and happiness of our teams.