Click here to close now.




















Welcome!

Microservices Expo Authors: AppDynamics Blog, Lori MacVittie, Trevor Parsons, Mike Kavis, Liz McMillan

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
The Internet of Things. Cloud. Big Data. Real-Time Analytics. To those who do not quite understand what these phrases mean (and let’s be honest, that’s likely to be a large portion of the world), words like “IoT” and “Big Data” are just buzzwords. The truth is, the Internet of Things encompasses much more than jargon and predictions of connected devices. According to Parker Trewin, Senior Director of Content and Communications of Aria Systems, “IoT is big news because it ups the ante: Reach out ...
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Auto-scaling environments, micro-service architectures and globally-distributed teams are just three common examples of why organizations today need automation and interoperability more than ever. But is interoperability something we simply start doing, or does it require a reexamination of our processes? And can we really improve our processes without first making interoperability a requirement for how we choose our tools?
Our guest on the podcast this week is Adrian Cockcroft, Technology Fellow at Battery Ventures. We discuss what makes Docker and Netflix highly successful, especially through their use of well-designed IT architecture and DevOps.
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Arch...
This week, I joined SOASTA as Senior Vice President of Performance Analytics. Given my background in cloud computing and distributed systems operations — you may have read my blogs on CNET or GigaOm — this may surprise you, but I want to explain why this is the perfect time to take on this opportunity with this team. In fact, that’s probably the best way to break this down. To explain why I’d leave the world of infrastructure and code for the world of data and analytics, let’s explore the timing...
Digital Transformation is the ultimate goal of cloud computing and related initiatives. The phrase is certainly not a precise one, and as subject to hand-waving and distortion as any high-falutin' terminology in the world of information technology. Yet it is an excellent choice of words to describe what enterprise IT—and by extension, organizations in general—should be working to achieve. Digital Transformation means: handling all the data types being found and created in the organizat...
Alibaba, the world’s largest ecommerce provider, has pumped over a $1 billion into its subsidiary, Aliya, a cloud services provider. This is perhaps one of the biggest moments in the global Cloud Wars that signals the entry of China into the main arena. Here is why this matters. The cloud industry worldwide is being propelled into fast growth by tremendous demand for cloud computing services. Cloud, which is highly scalable and offers low investment and high computational capabilities to end us...
Public Cloud IaaS started its life in the developer and startup communities and has grown rapidly to a $20B+ industry, but it still pales in comparison to how much is spent worldwide on IT: $3.6 trillion. In fact, there are 8.6 million data centers worldwide, the reality is many small and medium sized business have server closets and colocation footprints filled with servers and storage gear. While on-premise environment virtualization may have peaked at 75%, the Public Cloud has lagged in adop...
SYS-CON Events announced today that HPM Networks will exhibit at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. For 20 years, HPM Networks has been integrating technology solutions that solve complex business challenges. HPM Networks has designed solutions for both SMB and enterprise customers throughout the San Francisco Bay Area.
The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin,...
MuleSoft has announced the findings of its 2015 Connectivity Benchmark Report on the adoption and business impact of APIs. The findings suggest traditional businesses are quickly evolving into "composable enterprises" built out of hundreds of connected software services, applications and devices. Most are embracing the Internet of Things (IoT) and microservices technologies like Docker. A majority are integrating wearables, like smart watches, and more than half plan to generate revenue with ...
JavaScript is primarily a client-based dynamic scripting language most commonly used within web browsers as client-side scripts to interact with the user, browser, and communicate asynchronously to servers. If you have been part of any web-based development, odds are you have worked with JavaScript in one form or another. In this article, I'll focus on the aspects of JavaScript that are relevant within the Node.js environment.
One of the ways to increase scalability of services – and applications – is to go “stateless.” The reasons for this are many, but in general by eliminating the mapping between a single client and a single app or service instance you eliminate the need for resources to manage state in the app (overhead) and improve the distributability (I can make up words if I want) of requests across a pool of instances. The latter occurs because sessions don’t need to hang out and consume resources that could ...
Rapid innovation, changing business landscapes, and new IT demands force businesses to make changes quickly. The DevOps approach is a way to increase business agility through collaboration, communication, and integration across different teams in the IT organization. In his session at DevOps Summit, Chris Van Tuin, Chief Technologist for the Western US at Red Hat, will discuss: The acceleration of application delivery for the business with DevOps
Growth hacking is common for startups to make unheard-of progress in building their business. Career Hacks can help Geek Girls and those who support them (yes, that's you too, Dad!) to excel in this typically male-dominated world. Get ready to learn the facts: Is there a bias against women in the tech / developer communities? Why are women 50% of the workforce, but hold only 24% of the STEM or IT positions? Some beginnings of what to do about it! In her Opening Keynote at 16th Cloud Expo, S...
Software is eating the world. The more it eats, the bigger the mountain of data and wealth of valuable insights to digest and act on. Forward facing customer-centric IT organizations, leaders and professionals are looking to answer questions like how much revenue was lost today from platinum users not converting because they experienced poor mobile app performance. This requires a single, real-time pane of glass for end-to-end analytics covering business, customer, and IT operational data.
Approved this February by the Internet Engineering Task Force (IETF), HTTP/2 is the first major update to HTTP since 1999, when HTTP/1.1 was standardized. Designed with performance in mind, one of the biggest goals of HTTP/2 implementation is to decrease latency while maintaining a high-level compatibility with HTTP/1.1. Though not all testing activities will be impacted by the new protocol, it's important for testers to be aware of any changes moving forward.
"ProfitBricks was founded in 2010 and we are the painless cloud - and we are also the Infrastructure as a Service 2.0 company," noted Achim Weiss, Chief Executive Officer and Co-Founder of ProfitBricks, in this SYS-CON.tv interview at 16th Cloud Expo, held June 9-11, 2015, at the Javits Center in New York City.
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.