Click here to close now.



Welcome!

Microservices Expo Authors: Anders Wallgren, Pat Romanski, Jason Bloomberg, Liz McMillan, 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.

Transparency
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.

Accountability

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.

Holistic
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
As software organizations continue to invest in achieving Continuous Delivery (CD) of their applications, we see increased interest in microservices architectures, which–on the face of it–seem like a natural fit for enabling CD. In microservices (or its predecessor, “SOA”), the business functionality is decomposed into a set of independent, self-contained services that communicate with each other via an API. Each of the services has their own application release cycle, and are developed and depl...
With microservices, SOA and distributed architectures becoming more popular, it is becoming increasingly harder to keep track of where time is spent in a distributed application when trying to diagnose performance problems. Distributed tracing systems attempt to address this problem by following application requests across service boundaries, persisting metadata along the way that provide context for fine-grained performance monitoring.
The battle over bimodal IT is heating up. Now that there’s a reasonably broad consensus that Gartner’s advice about bimodal IT is deeply flawed – consensus everywhere except perhaps at Gartner – various ideas are springing up to fill the void. The bimodal problem, of course, is well understood. ‘Traditional’ or ‘slow’ IT uses hidebound, laborious processes that would only get in the way of ‘fast’ or ‘agile’ digital efforts. The result: incoherent IT strategies and shadow IT struggles that lead ...
More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes ho...
SYS-CON Events announced today that Commvault, a global leader in enterprise data protection and information management, has been named “Bronze Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY, and the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Commvault is a leading provider of data protection and information management...
SYS-CON Events announced today that AppNeta, the leader in performance insight for business-critical web applications, will exhibit and present at SYS-CON's @DevOpsSummit at Cloud Expo New York, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. AppNeta is the only application performance monitoring (APM) company to provide solutions for all applications – applications you develop internally, business-critical SaaS applications you use and the networks that deli...
SYS-CON Events announced today that Alert Logic, Inc., the leading provider of Security-as-a-Service solutions for the cloud, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Alert Logic, Inc., provides Security-as-a-Service for on-premises, cloud, and hybrid infrastructures, delivering deep security insight and continuous protection for customers at a lower cost than traditional security solutions. Ful...
If we look at slow, traditional IT and jump to the conclusion that just because we found its issues intractable before, that necessarily means we will again, then it’s time for a rethink. As a matter of fact, the world of IT has changed over the last ten years or so. We’ve been experiencing unprecedented innovation across the board – innovation in technology as well as in how people organize and accomplish tasks. Let’s take a look at three differences between today’s modern, digital context...
SYS-CON Events announced today that VAI, a leading ERP software provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. VAI (Vormittag Associates, Inc.) is a leading independent mid-market ERP software developer renowned for its flexible solutions and ability to automate critical business functions for the distribution, manufacturing, specialty retail and service sectors. An IBM Premier Business Part...
SYS-CON Events announced today that Catchpoint Systems, Inc., a provider of innovative web and infrastructure monitoring solutions, has been named “Silver Sponsor” of SYS-CON's DevOps Summit at 18th Cloud Expo New York, which will take place June 7-9, 2016, at the Javits Center in New York City, NY. Catchpoint is a leading Digital Performance Analytics company that provides unparalleled insight into customer-critical services to help consistently deliver an amazing customer experience. Designed...
The (re?)emergence of Microservices was especially prominent in this week’s news. What are they good for? do they make sense for your application? should you take the plunge? and what do Microservices mean for your DevOps and Continuous Delivery efforts? Continue reading for more on Microservices, containers, DevOps culture, and more top news from the past week. As always, stay tuned to all the news coming from@ElectricCloud on DevOps and Continuous Delivery throughout the week and retweet/favo...
In most cases, it is convenient to have some human interaction with a web (micro-)service, no matter how small it is. A traditional approach would be to create an HTTP interface, where user requests will be dispatched and HTML/CSS pages must be served. This approach is indeed very traditional for a web site, but not really convenient for a web service, which is not intended to be good looking, 24x7 up and running and UX-optimized. Instead, talking to a web service in a chat-bot mode would be muc...
In the Bimodal model we find two areas of IT - the traditional kind where the main concern is keeping the lights on and the IT focusing on agility and speed, where everything needs to be faster. Today companies are investing in new technologies and processes to emulate their most agile competitors. Gone are the days of waterfall development and releases only every few months. Today's IT and the business it powers demands performance akin to a supercar - everything needs to be faster, every sc...
At the heart of the Cloud Native model is a microservices application architecture, and applying this to a telco SDN scenario offers enormous opportunity for product innovation and competitive advantage. For example in the ETSI NFV Ecosystem white paper they describe one of the product markets that SDN might address to be the Home sector. Vendors like Alcatel market SDN-based solutions for the home market, offering Home Gateways – A virtual residential gateway (vRGW) where service provider...
SYS-CON Events announced today that Interoute, owner-operator of one of Europe's largest networks and a global cloud services platform, has been named “Bronze Sponsor” of SYS-CON's 18th Cloud Expo, which will take place on June 7-9, 2015 at the Javits Center in New York, New York. Interoute is the owner-operator of one of Europe's largest networks and a global cloud services platform which encompasses 12 data centers, 14 virtual data centers and 31 colocation centers, with connections to 195 ad...
Web performance issues and advances have been gaining a stronger presence in the headlines as people are becoming more aware of its impact on virtually every business, and 2015 was no exception. We saw a myriad of major outages this year hit some of the biggest corporations, as well as some technology integrations and other news that we IT Ops aficionados find very exciting. This past year has offered several opportunities for growth and evolution in the performance realm — even the worst failu...
Are you someone who knows that the number one rule in DevOps is “Don’t Panic”? Especially when it comes to making Continuous Delivery changes inside your organization? Are you someone that theorizes that if anyone implements real automation changes, the solution will instantly become antiquated and be replaced by something even more bizarre and inexplicable?
Welcome to the first top DevOps news roundup of 2016! At the end of last year, we saw some great predictions for 2016. While we’re excited to kick off the new year, this week’s top posts reminded us to take a second to slow down and really understand the current state of affairs. For example, do you actually know what microservices are – or aren’t? What about DevOps? Does the emphasis still fall mostly on the development side? This week’s top news definitely got the wheels turning and just migh...
Test automation is arguably the most important innovation to the process of QA testing in software development. The ability to automate regression testing and other repetitive test cases can significantly reduce the overall production time for even the most complex solutions. As software continues to be developed for new platforms – including mobile devices and the diverse array of endpoints that will be created during the rise of the Internet of Things - automation integration will have a huge ...
Providing a full-duplex communication channel over a single TCP connection, WebSocket is the most efficient protocol for real-time responses over the web. If you’re utilizing WebSocket technology, performance testing will boil down to simulating the bi-directional nature of your application. Introduced with HTML5, the WebSocket protocol allows for more interaction between a browser and website, facilitating real-time applications and live content. WebSocket technology creates a persistent conne...