Microservices Expo Authors: Pat Romanski, Elizabeth White, Mehdi Daoudi, Flint Brenton, Gordon Haff

Related Topics: @DevOpsSummit, Microservices Expo, Linux Containers, Containers Expo Blog, @CloudExpo

@DevOpsSummit: Blog Post

What Does an SLA Mean to You? | @DevOpsSummit #DevOps #SLA #ContinuousDelivery

You can factor performance and load testing into your continuous integration process by focusing on performance SLAs

When it comes to testing an application, many project managers and test leads do not fit performance and load testing early on in the development life cycle. Often, performance and load testing are conducted once the application has been completed and after all functional testing is done. In fact, it's frequently a last step - almost an afterthought - before the app is ready to go into production.

The problem with this approach is the classic problem with late-stage testing. When issues are found by the testers, developers have to go back and open up long-finalized code to fix them. There's risk in causing other parts of the application to break. Addressing problems after-the-fact becomes time consuming and expensive. Furthermore, any delay in releasing a new feature or a new app can directly impact revenue.

Even though you are running an agile development process, that doesn't necessarily mean that your performance testing is being conducted in a truly agile way. Saving performance testing for a "final sprint" before release still treats it like a waterfall development step, with all the cost and risk that comes with that. In this post, we will show you how to make load testing happen early and often by putting SLAs on the agile task board.

What Does an SLA Mean to You?
You can factor performance and load testing into your continuous integration process by focusing on performance SLAs, or service level agreements. Traditionally, SLAs are contracts put in place between two parties, such as a service firm and its client. This agreement sets various attributes about how the service will be delivered. For example, a large company that outsources its help desk operations to another company may require that all incoming emails be responded to within one hour. That agreement allows the client to build its business knowing that the desired service will be executed according to its specifications.

As a performance tester, you can think of an SLA in terms of your performance parameters. In your case, it's an implicit contract that you make with your user. It's almost like a standard that you hold your application to on behalf of your users. Your SLA may state that all pages need to load within 2 seconds, or that the first page of results of a search should be displayed within 4 seconds.

Though this isn't a hard-and-fast contract, that's how you want to think about it. Specify your SLA items during the application design process, and you can turn them into requirements that are placed on the task board as part of agile. That way, developers are taking performance into account as they develop the application, and not leaving it as an afterthought.

What Your SLA Should Include
There are all sorts of website metrics you can include in an SLA. The most important thing is to get something specified up front. This is how you are going to get developers coding for performance at the very beginning of the process.

When you are first starting, we recommend that you have enough specified in your performance SLAs to support automated smoke testing. Consider what happens in a smoke test. Once the application is built, it will be deployed and a series of tests will be run to make sure that everything works. This basic test might be as simple as setting up a user and having the user log in. Adding a performance SLA to that smoke test could be as simple as requiring that the login process be completed within a given time window.

Add that requirement to your task board, and suddenly you are automating performance testingright at the beginning of the development process. As more of the app gets developed, you can add more requirements alongside the modules and features being created.

When you create your SLAs, it's a good idea to identify a set of key pages to test regularly (home page, shopping cart, contact form, search results, chat window, etc.), and define requirements for a set of metrics such as:

  • DNS resolution time
  • Time-to-display
  • Time-to-last-byte
  • System uptime

Obviously your application will have its own critical performance metrics as well.

Finally, define a base level of network types (Wi-Fi, 3G) and platforms (operating systems and browsers) that your SLA will be measured from. Requiring zippy load times for someone running IE6 over a dial-up internet connection will only prompt hatred and ire from your developers, but providing realistic expectations that apply to the bulk of your users will keep everyone happy.

How Often to Conduct Load and Performance Testing
You now know how set expectations with SLAs in place, but how often should performance and load tests to be conducted? Remember, testing is happening throughout the agile development process, and at different scales. For many agile shops, your automated build process includes a number of tests that get executed every time a build happens. Then you may have additional testing that is done on a more thorough basis, but less frequently. Sometimes you have test scripts that are run every time code is checked in.

Match your automated performance testing to the process. It's unreasonable to expect a full load test be conducted every time the app is smoke tested, but something simple will match the scope, intent, and turn-around time of the smoke test, fitting in nicely with what's already happening. Use your best judgment and align your SLAs with the work being done, and you should be ok.

The SLA: One Secret to Quick and Efficient Load Testing
As your application grows and your process matures, you'll end up with a rich library of SLA requirements throughout your portfolio of test structures. You'll also have automated tests that can validate those SLAs within the right testing constructs: smoke testing, comprehensive automated tests, unit tests, and other areas. It won't take too many cycles for performance to become a regular expectation of the code that gets produced.

Photo Credit: Enrique Fernández

More Stories By Tim Hinds

Tim Hinds is the Product Marketing Manager for NeoLoad at Neotys. He has a background in Agile software development, Scrum, Kanban, Continuous Integration, Continuous Delivery, and Continuous Testing practices.

Previously, Tim was Product Marketing Manager at AccuRev, a company acquired by Micro Focus, where he worked with software configuration management, issue tracking, Agile project management, continuous integration, workflow automation, and distributed version control systems.

@MicroservicesExpo Stories
There is a huge demand for responsive, real-time mobile and web experiences, but current architectural patterns do not easily accommodate applications that respond to events in real time. Common solutions using message queues or HTTP long-polling quickly lead to resiliency, scalability and development velocity challenges. In his session at 21st Cloud Expo, Ryland Degnan, a Senior Software Engineer on the Netflix Edge Platform team, will discuss how by leveraging a reactive stream-based protocol,...
"We started a Master of Science in business analytics - that's the hot topic. We serve the business community around San Francisco so we educate the working professionals and this is where they all want to be," explained Judy Lee, Associate Professor and Department Chair at Golden Gate University, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
For over a decade, Application Programming Interface or APIs have been used to exchange data between multiple platforms. From social media to news and media sites, most websites depend on APIs to provide a dynamic and real-time digital experience. APIs have made its way into almost every device and service available today and it continues to spur innovations in every field of technology. There are multiple programming languages used to build and run applications in the online world. And just li...
The general concepts of DevOps have played a central role advancing the modern software delivery industry. With the library of DevOps best practices, tips and guides expanding quickly, it can be difficult to track down the best and most accurate resources and information. In order to help the software development community, and to further our own learning, we reached out to leading industry analysts and asked them about an increasingly popular tenet of a DevOps transformation: collaboration.
We call it DevOps but much of the time there’s a lot more discussion about the needs and concerns of developers than there is about other groups. There’s a focus on improved and less isolated developer workflows. There are many discussions around collaboration, continuous integration and delivery, issue tracking, source code control, code review, IDEs, and xPaaS – and all the tools that enable those things. Changes in developer practices may come up – such as developers taking ownership of code ...
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...
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.
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...
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"We are an integrator of carrier ethernet and bandwidth to get people to connect to the cloud, to the SaaS providers, and the IaaS providers all on ethernet," explained Paul Mako, CEO & CTO of Massive Networks, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
"Outscale was founded in 2010, is based in France, is a strategic partner to Dassault Systémes and has done quite a bit of work with divisions of Dassault," explained Jackie Funk, Digital Marketing exec at Outscale, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
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 ...