Welcome!

Microservices Expo Authors: Lori MacVittie, Elizabeth White, Daniel Khan, Liz McMillan, Pat Romanski

Related Topics: @CloudExpo, Microservices Expo, Containers Expo Blog, API Journal, 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
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
Ovum, a leading technology analyst firm, has published an in-depth report, Ovum Decision Matrix: Selecting a DevOps Release Management Solution, 2016–17. The report focuses on the automation aspects of DevOps, Release Management and compares solutions from the leading vendors.
No matter how well-built your applications are, countless issues can cause performance problems, putting the platforms they are running on under scrutiny. If you've moved to Node.js to power your applications, you may be at risk of these issues calling your choice into question. How do you identify vulnerabilities and mitigate risk to take the focus off troubleshooting the technology and back where it belongs, on innovation? There is no doubt that Node.js is one of today's leading platforms of ...
Adding public cloud resources to an existing application can be a daunting process. The tools that you currently use to manage the software and hardware outside the cloud aren’t always the best tools to efficiently grow into the cloud. All of the major configuration management tools have cloud orchestration plugins that can be leveraged, but there are also cloud-native tools that can dramatically improve the efficiency of managing your application lifecycle. In his session at 18th Cloud Expo, ...
SYS-CON Events announced today that LeaseWeb USA, a cloud Infrastructure-as-a-Service (IaaS) provider, will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. LeaseWeb is one of the world's largest hosting brands. The company helps customers define, develop and deploy IT infrastructure tailored to their exact business needs, by combining various kinds cloud solutions.
SYS-CON Events announced today that Venafi, the Immune System for the Internet™ and the leading provider of Next Generation Trust Protection, will exhibit at @DevOpsSummit at 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Venafi is the Immune System for the Internet™ that protects the foundation of all cybersecurity – cryptographic keys and digital certificates – so they can’t be misused by bad guys in attacks...
DevOps at Cloud Expo – being held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's largest enterprises – and delivering real results. Am...

Let's just nip the conflation of these terms in the bud, shall we?

"MIcro" is big these days. Both microservices and microsegmentation are having and will continue to have an impact on data center architecture, but not necessarily for the same reasons. There's a growing trend in which folks - particularly those with a network background - conflate the two and use them to mean the same thing.

They are not.

One is about the application. The other, the network. T...

The 19th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Digital Transformation, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportuni...
If you are within a stones throw of the DevOps marketplace you have undoubtably noticed the growing trend in Microservices. Whether you have been staying up to date with the latest articles and blogs or you just read the definition for the first time, these 5 Microservices Resources You Need In Your Life will guide you through the ins and outs of Microservices in today’s world.
Before becoming a developer, I was in the high school band. I played several brass instruments - including French horn and cornet - as well as keyboards in the jazz stage band. A musician and a nerd, what can I say? I even dabbled in writing music for the band. Okay, mostly I wrote arrangements of pop music, so the band could keep the crowd entertained during Friday night football games. What struck me then was that, to write parts for all the instruments - brass, woodwind, percussion, even k...
This digest provides an overview of good resources that are well worth reading. We’ll be updating this page as new content becomes available, so I suggest you bookmark it. Also, expect more digests to come on different topics that make all of our IT-hearts go boom!
Keeping pace with advancements in software delivery processes and tooling is taxing even for the most proficient organizations. Point tools, platforms, open source and the increasing adoption of private and public cloud services requires strong engineering rigor – all in the face of developer demands to use the tools of choice. As Agile has settled in as a mainstream practice, now DevOps has emerged as the next wave to improve software delivery speed and output. To make DevOps work, organization...
SYS-CON Events announced today that Isomorphic Software will exhibit at DevOps Summit at 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Isomorphic Software provides the SmartClient HTML5/AJAX platform, the most advanced technology for building rich, cutting-edge enterprise web applications for desktop and mobile. SmartClient combines the productivity and performance of traditional desktop software with the simp...
Internet of @ThingsExpo, taking place November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with the 19th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world and ThingsExpo Silicon Valley Call for Papers is now open.
Right off the bat, Newman advises that we should "think of microservices as a specific approach for SOA in the same way that XP or Scrum are specific approaches for Agile Software development". These analogies are very interesting because my expectation was that microservices is a pattern. So I might infer that microservices is a set of process techniques as opposed to an architectural approach. Yet in the book, Newman clearly includes some elements of concept model and architecture as well as p...
This is a no-hype, pragmatic post about why I think you should consider architecting your next project the way SOA and/or microservices suggest. No matter if it’s a greenfield approach or if you’re in dire need of refactoring. Please note: considering still keeps open the option of not taking that approach. After reading this, you will have a better idea about whether building multiple small components instead of a single, large component makes sense for your project. This post assumes that you...
In his session at @DevOpsSummit at 19th Cloud Expo, Yoseph Reuveni, Director of Software Engineering at Jet.com, will discuss Jet.com's journey into containerizing Microsoft-based technologies like C# and F# into Docker. He will talk about lessons learned and challenges faced, the Mono framework tryout and how they deployed everything into Azure cloud. Yoseph Reuveni is a technology leader with unique experience developing and running high throughput (over 1M tps) distributed systems with extre...
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
Node.js and io.js are increasingly being used to run JavaScript on the server side for many types of applications, such as websites, real-time messaging and controllers for small devices with limited resources. For DevOps it is crucial to monitor the whole application stack and Node.js is rapidly becoming an important part of the stack in many organizations. Sematext has historically had a strong support for monitoring big data applications such as Elastic (aka Elasticsearch), Cassandra, Solr, S...