Welcome!

Microservices Expo Authors: Elizabeth White, Gopala Krishna Behara, Sridhar Chalasani, Tirumala Khandrika, Kelly Burford

Related Topics: @CloudExpo, Microservices Expo, Containers Expo Blog, Cognitive Computing , Agile Computing, Apache, Cloud Security

@CloudExpo: Article

Cloudwashing the Cloud Brokerage

Cloud Brokerages are a hot topic - for better or worse.

Since ZapThink wrote our ZapFlash on Cloud Brokerages in April 2011, the Cloud Brokerage marketplace has exploded. Or at the very least, the noise level involving such Brokerages has reached a fever pitch, which the vendors in the space want you to think is the sound of an exploding market anyway. Regardless of your level of cynicism, however, there’s no question that Cloud Brokerages are a hot topic. But as with so many new markets, confusion reigns—in large part because such Brokerages come in so many different flavors. That being said, this market also suffers from rampant Cloudwashing, which refers to vendors (and service providers) who stick the “Cloud” label on existing offerings to take advantage of the Cloud hype. Let’s see if we can separate the steak from the sizzle and delineate how Cloud Brokerages are actually supposed to work.

Gartner: Cloudwashing Facilitator
For better or worse, many people turn to Gartner when they have questions about nascent IT markets. Gartner, however, is a vendor-driven market research firm, rather than a purveyor of vendor-independent best practices. Their research on Cloud Brokerages is a case in point. Gartner defines a Cloud Service Brokerage (CSB) as being composed of three core roles: aggregation, integration, and customization. They point out that the role of Aggregation Broker aligns with the traditional distributor role; the Integration Broker corresponds to the system integrator (SI); and the Customization Broker similarly aligns with the independent software vendor (ISV).

What’s wrong with this picture is that distributors, SIs, and in particular ISVs pay most of Gartner’s bills. So when they conduct their research, they talk to their customers and find out what kinds of CSBs they’re offering. And what do those customers say? I’m a distributor, but now I’m a Cloud Aggregation Broker! I’m an SI, but now I’m a Cloud Integration Broker! And most tellingly: I’m a software vendor, but now I’m a Cloud Customization Broker! It doesn’t really matter if any of these players have something that actually works, or even if it does, it may have little or nothing to do with the Cloud, and there’s no guarantee that any enterprise buyer will actually want what they’re peddling. But hey, it’s an emerging market, so what do you expect?

Contrast Gartner’s list of CSB roles with those from the US Department of Commerce’s National Institute for Standards and Technology (NIST). According to NIST’s Cloud Conceptual Reference Diagram, CSBs have three core capabilities: aggregation, arbitrage, and intermediation. Yes, NIST and Gartner both agree on the importance of aggregation, but that’s where the meeting of minds diverges. NIST calls for arbitrage (support for dynamic pricing in a Cloud services marketplace), but arbitrage isn’t on Gartner’s list. Why not? Perhaps because Gartner didn’t have any Cloud arbitrage vendors to interview when they did their research? Your guess is as good as ours.

As for intermediation, NIST has something quite different in mind from Cloud integration. When a Brokerage intermediates between Cloud customers and Cloud Service Providers (CSPs), the Brokerage provides a range of business-related capabilities, including assurance, consolidated invoicing, and SLA management, independent of whether the Brokerage is also providing integration capabilities between Cloud customers and CSPs. True, CSBs may end up offering integration as well, but more likely as an advanced capability that will become a reality down the road a few years. So why has Gartner included it and not intermediation? Because of the SIs, as well as the B2B integration vendors who have all Cloudwashed their offerings into Cloud Integration Brokerages.

The Two Cloud Brokerage Lifecycles
Instead of taking a vendor-centric perspective on CSBs, let’s think about how people might actually use them. There are two basic types of users for a CSB: the CSP who wishes to make its offering available in the Brokerage, and the Cloud customer who is looking for services from a CSP and is calling upon the CSB to help in some fashion. We expect such customers to be large enterprises who have several departments or divisions who wish to access Cloud services. For such organizations, the Brokerage serves to present a single face to the CSPs while supporting each department’s individual requirements for Cloud services.

To understand the role of the CSB, let’s start with the lifecycle from the CSP’s perspective:

  1. Registration – The CSP must register with the Brokerage in order to begin the enrollment process.

  2. Certification/Assessment – The CSB will assess the candidate CSPs and certify the ones that qualify to join the Brokerage.

  3. Enrollment – The CSP follows the Brokerage’s process for making its services available via the Brokerage.

  4. Negotiation – Once a customer selects the CSP through the Brokerage, the parties must negotiate a business arrangement. The Brokerage may act as an intermediary or simply hand off the negotiation to the two parties.

  5. Provisioning – The Brokerage may assist the CSP in provisioning Cloud resources for the customer.

  6. Management – Management comes in two flavors: business management, where the Brokerage handles invoicing, payments, and other business interactions on behalf of the parties; and technical management, where the Brokerage assists in SLA monitoring and other technical management tasks.

  7. Assurance – The Brokerage may provide auditing and other assurance activities on behalf of customers to insure CSPs are in compliance with required regulations and other policies.

  8. Integration – In some cases the Brokerage may act as an integration hub between CSPs and customers.

  9. Support – The CSP must support the customer, and the CSB may act as an intermediary for such support.

  10. Deprovisioning – If the customer wishes to discontinue a relationship, the Brokerage may assist with deprovisioning. This step may include delivering data to the customer, confirming customer data no longer reside in the Cloud environment, and wrapping up the business relationship. If the relationship between CSP and customer went south, the CSB may even be called upon to provide litigation support.

Now, let’s take a look at the CSB lifecycle from the Cloud customer’s perspective:

  1. Research – The CSB must provide information to potential customers so that they can make informed decisions about Cloud options available to them through the Brokerage.

  2. Qualification – The customer enters its criteria for Cloud services into the Brokerage, and the Brokerage should only show CSPs and individual Cloud services that meet the customer’s requirements.

  3. Assessment – The CSB may assess the customer’s business or technical environment in order to gauge suitability for particular services available through the Brokerage.

  4. Selection – The customer selects services through the Brokerage.

  5. Negotiation – The Brokerage supports the ability for customers and CSPs to negotiate business terms, either by facilitating direct communication or via automated intermediation, which would typically include arbitrage capabilities.

  6. Acceptance – The customer is able to accept the business terms it selects via the Brokerage.

  7. Onboarding – The Brokerage supports the customer’s efforts to provision Cloud resources, either by facilitating direct interactions between customer and CSP or via an automated onboarding capability.

  8. Management – Management appears on both the CSP and customer lifecycles because it always involves managing the relationships between the two (both business and technical).

  9. Assurance – Assurance also involves both customer and CSP. The Brokerage may take a limited or active role. The CSB will interface with the organization’s Information Assurance organization, but the CSB’s involvement doesn’t absolve the CSP or the Cloud customer from performing their due diligence in meeting their respective security and compliance objectives.

  10. Integration – When the Brokerage acts as an integration hub.

  11. Failover – Many customers will use the Brokerage to handle switching from one CSP to another. Such failover may occur as the result of a technical problem (e.g., a denial of service attack brings down the primary CSP) or a business problem (the primary CSP no longer offers the best deal, or in the extreme case, the CSP goes out of business).

  12. Offboarding – The Brokerage may also handle wrapping up business loose ends should the customer cancel its relationship with a CSP.

The ZapThink Take
The point to listing so many steps on the two CSB lifecycles isn’t to propose a final definition of such lifecycles, of course – the market is far too young for that. If anything, they are wish lists for what we might want Cloud Brokerages to do for us, based not on Brokerage-related products and services on the market today, but rather on what people expect Cloud Brokerages to do. But as with any technical capability, what you want it to do depends upon the core business problems you’re looking to solve. In the case of Cloud Brokerages, there remains a rather diverse set of potential business drivers that is leading the marketplace to grow in a complex, messy fashion.

Not only will individual organizations’ requirements for Brokerages differ, ZapThink is also seeing divergence of requirements among industries. In particular, the US Federal Government is very interested in Cloud Brokerages, with Requests for Information from the General Services Administration (GSA) as well as the Defense Information Systems Agency (DISA). In both cases, one of the Government’s key requirements is to support fair competition among CSPs – contrary to private sector customers, who couldn’t care less about such competition, except insofar as it leads to lower prices in the marketplace.

In some ways, the Government is like any other large enterprise. It has hundreds of agencies, each of which may have dozens of individual programs, all clamoring for Cloud services. They are looking to Brokerages to support the ability for such programs to select the best CSP offering for their needs, while providing the best overall value to the Government as a whole. On the other hand, in its role of promoting the general welfare of the people of the US, it is uniquely qualified to foster competition among CSPs and Cloud vendors, leading to better quality and lower prices for everyone.

Image credit: Karen and Brad Emerson

More Stories By Jason Bloomberg

Jason Bloomberg is the leading expert on architecting agility for the enterprise. As president of Intellyx, Mr. Bloomberg brings his years of thought leadership in the areas of Cloud Computing, Enterprise Architecture, and Service-Oriented Architecture to a global clientele of business executives, architects, software vendors, and Cloud service providers looking to achieve technology-enabled business agility across their organizations and for their customers. His latest book, The Agile Architecture Revolution (John Wiley & Sons, 2013), sets the stage for Mr. Bloomberg’s groundbreaking Agile Architecture vision.

Mr. Bloomberg is perhaps best known for his twelve years at ZapThink, where he created and delivered the Licensed ZapThink Architect (LZA) SOA course and associated credential, certifying over 1,700 professionals worldwide. He is one of the original Managing Partners of ZapThink LLC, the leading SOA advisory and analysis firm, which was acquired by Dovel Technologies in 2011. He now runs the successor to the LZA program, the Bloomberg Agile Architecture Course, around the world.

Mr. Bloomberg is a frequent conference speaker and prolific writer. He has published over 500 articles, spoken at over 300 conferences, Webinars, and other events, and has been quoted in the press over 1,400 times as the leading expert on agile approaches to architecture in the enterprise.

Mr. Bloomberg’s previous book, Service Orient or Be Doomed! How Service Orientation Will Change Your Business (John Wiley & Sons, 2006, coauthored with Ron Schmelzer), is recognized as the leading business book on Service Orientation. He also co-authored the books XML and Web Services Unleashed (SAMS Publishing, 2002), and Web Page Scripting Techniques (Hayden Books, 1996).

Prior to ZapThink, Mr. Bloomberg built a diverse background in eBusiness technology management and industry analysis, including serving as a senior analyst in IDC’s eBusiness Advisory group, as well as holding eBusiness management positions at USWeb/CKS (later marchFIRST) and WaveBend Solutions (now Hitachi Consulting).

@MicroservicesExpo Stories
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone in...
Many IT organizations have come to learn that leveraging cloud infrastructure is not just unavoidable, it’s one of the most effective paths for IT organizations to become more responsive to business needs. Yet with the cloud comes new challenges, including minimizing downtime, decreasing the cost of operations, and preventing employee burnout to name a few. As companies migrate their processes and procedures to their new reality of a cloud-based infrastructure, an incident management solution...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
Gaining visibility in today’s sprawling cloud infrastructure is complex and laborious, involving drilling down into tools offered by various cloud services providers. Enterprise IT organizations need smarter and effective tools at their disposal in order to address this pertinent problem. Gaining a 360 - degree view of the cloud costs requires collection and analysis of the cost data across all cloud infrastructures used inside an enterprise.
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
Our work, both with clients and with tools, has lead us to wonder how it is that organizations are handling compliance issues in the cloud. The big cloud vendors offer compliance for their infrastructure, but the shared responsibility model requires that you take certain steps to meet compliance requirements. Which lead us to start poking around a little more. We wanted to get a picture of what was available, and how it was being used. There is a lot of fluidity in this space, as in all things ...
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
The notion of improving operational efficiency is conspicuously absent from the healthcare debate - neither Obamacare nor the newly proposed GOP plan discusses the impact that a step-function improvement in efficiency could have on access to healthcare (through more capacity), quality of healthcare services (through reduced wait times for patients) or cost (through better utilization of scarce, expensive assets).
Admiral Calcote - also known as Lee Calcote (@lcalcote) or the Ginger Geek to his friends - gave a presentation entitled Characterizing and Contrasting Container Orchestrators at the 2016 All Day DevOps conference. Okay, he isn't really an admiral - nor does anyone call him that - but he used the title admiral to describe what container orchestrators do, relating it to an admiral directing a fleet of container ships. You could also say that they are like the conductor of an orchestra, directing...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
Recent survey done across top 500 fortune companies shows almost 70% of the CIO have either heard about IAC from their infrastructure head or they are on their way to implement IAC. Yet if you look under the hood while some level of automation has been done, most of the infrastructure is still managed in much tradition/legacy way. So, what is Infrastructure as Code? how do you determine if your IT infrastructure is truly automated?
Every few years, a disruptive force comes along that prompts us to reframe our understanding of what something means, or how it works. For years, the notion of what a computer is and how you make one went pretty much unchallenged. Then virtualization came along, followed by cloud computing, and most recently containers. Suddenly the old rules no longer seemed to apply, or at least they didn’t always apply. These disruptors made us reconsider our IT worldview.