Click here to close now.


Microservices Expo Authors: Pat Romanski, AppDynamics Blog, Liz McMillan, XebiaLabs Blog, Elizabeth White

Related Topics: Microservices Expo, Microsoft Cloud, API Journal, IoT User Interface, Agile Computing, Cloud Security

Microservices Expo: Blog Post

Your Service Level Agreement Stinks

Here’s what to look for – or avoid – in an SLA

When you're dealing with something as critical as your business infrastructure, you want to be sure that you'll get what you signed up for. If a company promises something, and you promise your colleagues something based on it, you want it to happen. That's where the service level agreement comes in. It's part of your contract that tells you what to expect and what happens if the company fails to meet those marks. Simple enough, right? Wrong.

Not all service level agreements are created equal. At a minimum, an SLA will formally define the services in a contract. In their highest forms, SLAs embody the values and capabilities of an entire organization, and they provide a clear benchmark for employee performance and customer satisfaction. If you are comparing IT service providers, it's time to set the bar high. Simply put, you want an SLA that is transparent, accountable, holistic, and logical for the provider. Here's how to spot it.

Most SLAs
Typical SLAs are buried in 20 pages of legalese. If you can find it, and cut through all the jargon, you might gain a vague idea of what will happen when your service provider fails you. And when your service experiences a disruption - which will eventually happen in one form, no matter which provider you choose - it will fall on you to translate the SLA and request credit, and of course, the company will make it as tiresome as possible to get your money.

Few customers actually get rebated by companies like this, and that, I can assure you, is a business strategy. If you provide a strong service, you don't need to hide behind a labyrinth of legal jargon. And if you are a customer, you do not want to entrust your IT infrastructure or assets with a company that is opaque, indifferent, and irresponsible.

Good providers tell their customers exactly what they're going to get, and tell them exactly what is going on at all times. This is all that customers ask. Speed, though desirable, can never compensate for unpredictability and deceptiveness. An enlightened SLA needs to detail specific, measurable commitments that tell customers what service they will receive, how quickly they're going to receive it, and what happens if they don't get that service.

Let me give a clear example from my experience with IT infrastructure hosting and cloud computing at SingleHop. We have an SLA we call the "Customer Bill of Rights." It more or less anchors every facet of our service. It is in fact an extension of our entire system. We operate on a principle called "Operational Transparency." This means that if a server goes down, we update affected clients in real time. If they wonder "have our servers gone down? If so, how long have they been down this quarter?" or "how much time do I wait for a response from tech support?" they can view a digital Report Card that details each item in their SLA and shows continuously updated data on how SingleHop is performing relative to each agreement. That is transparency. When you combine operational transparency with a detailed SLA, it turns all the usual mirrors around into clear glass.


What happens when a company messes up? Well, several things can happen:

  1. Irate customers cancel their contract.
  2. Irate customers invite their provider to a brawl in the legal ring.
  3. Irate customers watch their provider take responsibility and then respect them for it.

Everyone should prefer option #3. Cancelling a contract and shifting providers is costly and legal battles are very expensive. Migrations are dangerous and can disrupt business. You want an SLA that holds your provider accountable for any failures - be they outages or just slow responses. You should know the exact deployment time for a server and know exactly how much you will be credited if your service provider exceeds that time. You should know the expected response time from tech support, and know exactly how much you will be compensated if they take longer.

You know all this information not because you've been timing your service provider, but because they offer this information upfront. Don't work with a company that you must lasso and tie-down for a rebate.

How many interactions does the SLA cover? And, do items in the SLA conflict? For example, if an SLA promises support updates every three hours, but does not give a first response time, what good is the SLA? You could still bleed money for eight hours before getting a life raft. Great SLAs are comprehensive and holistic. They encourage customer-provider symbiosis. The best SLAs actually play into the interests of the provider - remember, they want lots of happy, sustainable customers.

As a customer, map out your anticipated interactions. If the SLA covers each interaction, it is holistic. If not, you can do or request better.

Understanding What's Not Mentioned
There are a lot of different aspects to an IaaS SLA that should but are not always mentioned. These are obvious to providers but not all customers see them right away. How fast does it take to replace a broken hard drive? Does the company keep replacement parts in stock or does it need to order them? Is there a senior tech available at all hours, and if so, how fast do escalations take? Make a list of the concerns you have, talk to people who have been through it and ask lots of questions. Sometimes when something is omitted, it's omitted for a reason.

Business Logic
Finally, a great SLA should be good for the receiver and the provider. If you are the customer, you should want transparency, accountability, and comprehensiveness to be in the interest of your service provider. Why? Because in an ideal world, you can rely on the same IT infrastructure for years and years, and frankly, that means your provider must succeed. And, if meeting the SLA is in the interest of the provider, then the provider will probably use it to evaluate their employees, sift out the bad eggs, and measure company-wide improvement. If, however, the SLA is against the interests of the company, then your provider may in fact discourage its employees from being too forthcoming and helpful.

Think about an SLA as the ‘moral' code for a company. If being "good" actual falls in line with a company's desire for profit, then that company is more likely to follow their code. If being "good" exacts cruel and unusual punishment on a company, then they will prefer to be "bad." Look for alignment between a company's interests and SLA. If they disagree, run for the hills.

Be Fruitful and Provide
A Service Level Agreement is a template for how a business intends to interact with customers. If it is transparent, accountable, holistic, and business-savvy, it is a winner. If you need a machete and $400 per hour guide to find it in the legal jungle and understand it, it is time to explore other options.

More Stories By Dan Ushman

Dan Ushman, Co-Founder and CMO of SingleHop, focuses on the company’s global marketing strategy and operations. He regularly attends and speaks at industry and marketing events. As a recognized thought leader in online marketing, Dan is one of the few internet marketing professionals to hold a Horizon Award for Marketing Innovation. When he isn’t working, he can be found in his kitchen whipping up homemade BBQ sauce, or in front of the grill with a spatula putting that sauce to work.

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
SYS-CON Events announced today that G2G3 will exhibit at SYS-CON's @DevOpsSummit Silicon Valley, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Based on a collective appreciation for user experience, design, and technology, G2G3 is uniquely qualified and motivated to redefine how organizations and people engage in an increasingly digital world.
If you are new to Python, you might be confused about the different versions that are available. Although Python 3 is the latest generation of the language, many programmers still use Python 2.7, the final update to Python 2, which was released in 2010. There is currently no clear-cut answer to the question of which version of Python you should use; the decision depends on what you want to achieve. While Python 3 is clearly the future of the language, some programmers choose to remain with Py...
“All our customers are looking at the cloud ecosystem as an important part of their overall product strategy. Some see it evolve as a multi-cloud / hybrid cloud strategy, while others are embracing all forms of cloud offerings like PaaS, IaaS and SaaS in their solutions,” noted Suhas Joshi, Vice President – Technology, at Harbinger Group, in this exclusive Q&A with Cloud Expo Conference Chair Roger Strukhoff.
Opinions on how best to package and deliver applications are legion and, like many other aspects of the software world, are subject to recurring trend cycles. On the server-side, the current favorite is container delivery: a “full stack” approach in which your application and everything it needs to run are specified in a container definition. That definition is then “compiled” down to a container image and deployed by retrieving the image and passing it to a container runtime to create a running...
Clearly the way forward is to move to cloud be it bare metal, VMs or containers. One aspect of the current public clouds that is slowing this cloud migration is cloud lock-in. Every cloud vendor is trying to make it very difficult to move out once a customer has chosen their cloud. In his session at 17th Cloud Expo, Naveen Nimmu, CEO of Clouber, Inc., will advocate that making the inter-cloud migration as simple as changing airlines would help the entire industry to quickly adopt the cloud wit...
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ab...
Apps and devices shouldn't stop working when there's limited or no network connectivity. Learn how to bring data stored in a cloud database to the edge of the network (and back again) whenever an Internet connection is available. In his session at 17th Cloud Expo, Bradley Holt, Developer Advocate at IBM Cloud Data Services, will demonstrate techniques for replicating cloud databases with devices in order to build offline-first mobile or Internet of Things (IoT) apps that can provide a better, ...
Despite all the talk about public cloud services and DevOps, you would think the move to cloud for enterprises is clear and simple. But in a survey of almost 1,600 IT decision makers across the USA and Europe, the state of the cloud in enterprise today is still fraught with considerable frustration. The business case for apps in the real world cloud is hybrid, bimodal, multi-platform, and difficult. Download this report commissioned by NTT Communications to see the insightful findings – registra...
Application availability is not just the measure of “being up”. Many apps can claim that status. Technically they are running and responding to requests, but at a rate which users would certainly interpret as being down. That’s because excessive load times can (and will be) interpreted as “not available.” That’s why it’s important to view ensuring application availability as requiring attention to all its composite parts: scalability, performance, and security.
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.
There once was a time when testers operated on their own, in isolation. They’d huddle as a group around the harsh glow of dozens of CRT monitors, clicking through GUIs and recording results. Anxiously, they’d wait for the developers in the other room to fix the bugs they found, yet they’d frequently leave the office disappointed as issues were filed away as non-critical. These teams would rarely interact, save for those scarce moments when a coder would wander in needing to reproduce a particula...
All we need to do is have our teams self-organize, and behold! Emergent design and/or architecture springs up out of the nothingness! If only it were that easy, right? I follow in the footsteps of so many people who have long wondered at the meanings of such simple words, as though they were dogma from on high. Emerge? Self-organizing? Profound, to be sure. But what do we really make of this sentence?
As we increasingly rely on technology to improve the quality and efficiency of our personal and professional lives, software has become the key business differentiator. Organizations must release software faster, as well as ensure the safety, security, and reliability of their applications. The option to make trade-offs between time and quality no longer exists—software teams must deliver quality and speed. To meet these expectations, businesses have shifted from more traditional approaches of d...
Information overload has infiltrated our lives. From the amount of news available and at our fingertips 24/7, to the endless choices we have when making a simple purchase, to the quantity of emails we receive on a given day, it’s increasingly difficult to sift out the details that really matter. When you envision your cloud monitoring system, the same thinking applies. We receive a lot of useless data that gets fed into the system, and the reality is no one in IT or DevOps has the time to manu...
Last month, my partners in crime – Carmen DeArdo from Nationwide, Lee Reid, my colleague from IBM and I wrote a 3-part series of blog posts on We titled our posts the Simple Math, Calculus and Art of DevOps. I would venture to say these are must-reads for any organization adopting DevOps. We examined all three ascpects – the Cultural, Automation and Process improvement side of DevOps. One of the key underlying themes of the three posts was the need for Cultural change – things like t...
It is with great pleasure that I am able to announce that Jesse Proudman, Blue Box CTO, has been appointed to the position of IBM Distinguished Engineer. Jesse is the first employee at Blue Box to receive this honor, and I’m quite confident there will be more to follow given the amazing talent at Blue Box with whom I have had the pleasure to collaborate. I’d like to provide an overview of what it means to become an IBM Distinguished Engineer.
I’ve been thinking a bit about microservices (μServices) recently. My immediate reaction is to think: “Isn’t this just yet another new term for the same stuff, Web Services->SOA->APIs->Microservices?” Followed shortly by the thought, “well yes it is, but there are some important differences/distinguishing factors.” Microservices is an evolutionary paradigm born out of the need for simplicity (i.e., get away from the ESB) and alignment with agile (think DevOps) and scalable (think Containerizati...
The cloud has reached mainstream IT. Those 18.7 million data centers out there (server closets to corporate data centers to colocation deployments) are moving to the cloud. In his session at 17th Cloud Expo, Achim Weiss, CEO & co-founder of ProfitBricks, will share how two companies – one in the U.S. and one in Germany – are achieving their goals with cloud infrastructure. More than a case study, he will share the details of how they prioritized their cloud computing infrastructure deployments ...
DevOps Summit at Cloud Expo 2014 Silicon Valley was a terrific event for us. The Qubell booth was crowded on all three days. We ran demos every 30 minutes with folks lining up to get a seat and usually standing around. It was great to meet and talk to over 500 people! My keynote was well received and so was Stan's joint presentation with RingCentral on Devops for BigData. I also participated in two Power Panels – ‘Women in Technology’ and ‘Why DevOps Is Even More Important than You Think,’ both ...