Click here to close now.


Microservices Expo Authors: Pat Romanski, Tim Hinds, Sanjeev Sharma, Blue Box Blog, Elizabeth White

Related Topics: Microservices Expo, Java IoT, Microsoft Cloud, IoT User Interface, Agile Computing, @CloudExpo

Microservices Expo: Article

Load Testing: Same Old, Same Old or a Whole New Ball Game?

How can we be prepared for the future of load and performance testing?

Bonjour Foxes!

I started my career as a Telecom Engineer for Rational Software in the load testing space back in the late '90s, and when I look back on the last decade, there were enormous advances in the broader IT world including development methodologies, processing speeds, network speeds, mobile devices (it's hard to believe the first iPhone was only released 6 years ago). But the question is: Has the world of load and performance testing really changed all that much? Are the missions the same? Are the challenges different? And how can we be prepared for the future of load and performance testing?

Let's start with what hasn't changed:

Websites crash.
Crashes are a reality today just as much as they were 10 years ago. While many companies have become aware of big events (e.g., Cyber Monday, big ad campaigns) that cause traffic spikes, exact traffic levels are still difficult to predict. One big difference between now and then is the sheer number of websites on the Internet. According to Netcraft, the number of active sites on the Internet has increased by almost 1000% over the past ten years. More websites = more crashes.

Developers still think their code is bug-free.
Being a load tester can sometimes come with the occasional power trip that results from crashing an application written by developers who think their code is perfect. While I'm sure their code is very good, load testing can still quickly uncover any flaws in the code or architecture that can cause performance issues.

Load testing is still pushed off until late in the development cycle.
This is a reality most testers just have to deal with. Testing in general, but particularly load and performance testing, are held off until the end of the development cycle, which can be particularly frustrating for testers who can be blamed for holding up a release.

HTTP is still a connectionless protocol.
Furthermore, it's being used to drive a world that is becoming increasingly connected. In fact, the vast majority of advances in web technologies (cookies, sessions, AJAX, WebSockets, SPDY, etc.) have been created in order to overcome the HTTP connectionless limitations. For load testers, this means it still causes complications.

What Has Changed?
Load testing is becoming a mandatory step in the development process.

I've been talking to more and more companies these days that are requiring that all applications go through load and performance testing before they're deployed to production. This is especially true for new online services that know that they only have one chance to show their best or likely lose that customer forever.

The performance of applications is becoming more important than the breadth of functionality.
For some companies like insurance and banks, the importance of application performance is much higher than the pure number of functions their apps can perform. This means that load and performance testers are playing more prominent roles within these development organizations.

The number of technologies built over HTTP is growing each month.
More and more technologies are being developed to make the web faster, more secure and more reactive, and more and more development organizations are adopting them at faster rates. This means load testers are required to test apps containing complex technologies they've never seen before, and it's no easy task to test apps utilizing AJAX, SPDY, WebSockets, video streaming, etc.

App developers have to consider the performance of their apps on mobile devices and networks.
Morgan Stanley
has predicted that mobile Internet users will surpass desktop Internet users by the end of the year. With this in mind, performance testers need to be able to re-create the use cases and network conditions actual users will experience with several different network types and several different devices.

What can you do to handle the realities of today and be prepared for load testing world of tomorrow?

1. Don't avoid load and performance testing.
If you're one of those people who think your apps will be fine and users will do the testing in production, I hope for your sake that your developers actually do write bug-free code. Remember, your end-users will not be as forgiving or as patient as virtual users are when your application is under high load if you recall the old statistic about losing 1% of sales for every 100 ms delay in response times.

2. Make your tests as realistic as possible.
Load testing is much easier these days with the tools available, but don't think it's a "point & click" operation. I see too many companies running "load tests" that do not simulate the number of users observed in production nor the conditions under which the apps will be used.

3. Make sure your load testing tool can match the rhythm of the technical "dance".
Developers and architects are going to want to take advantage of the latest technologies, even some that are still in beta. As a tester, you and your tool shouldn't be the bottleneck for the product launch. Make sure your tool supports your needs as well as the needs of your development organization.

With all of the advances in web and mobile application technologies and the instant response times end-users expect these days, the performance of applications is only going to grow in importance. My advice to load testers is to stay on top of these trends because they move quickly. It's certainly an exciting time to be a load tester.

More Stories By Hervé Servy

Hervé Servy is a Senior Performance Engineer at Neotys. He has spent 10 years working for IBM-Rational and Microsoft pre-sales and marketing in France and the Middle East. During the past 3 years, as a personal project, Hervé founded a nonprofit organization in the health 2.0 area. If that isn’t techie enough, Hervé was also born on the very same day Apple Computer was founded.

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
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at @DevOpsSummit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
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...
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...
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.
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 ...
Ten years ago, there may have been only a single application that talked directly to the database and spit out HTML; customer service, sales - most of the organizations I work with have been moving toward a design philosophy more like unix, where each application consists of a series of small tools stitched together. In web example above, that likely means a login service combines with webpages that call other services - like enter and update record. That allows the customer service team to writ...
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...
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...
SYS-CON Events announced today that Dyn, the worldwide leader in Internet Performance, will exhibit at SYS-CON's 17th International Cloud Expo®, which will take place on November 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Dyn is a cloud-based Internet Performance company. Dyn helps companies monitor, control, and optimize online infrastructure for an exceptional end-user experience. Through a world-class network and unrivaled, objective intelligence into Internet condit...
Between the compelling mockups and specs produced by analysts, and resulting applications built by developers, there exists a gulf where projects fail, costs spiral, and applications disappoint. Methodologies like Agile attempt to address this with intensified communication, with partial success but many limitations. In his session at DevOps Summit, Charles Kendrick, CTO and Chief Architect at Isomorphic Software, will present a revolutionary model enabled by new technologies. Learn how busine...
Achim Weiss is Chief Executive Officer and co-founder of ProfitBricks. In 1995, he broke off his studies to co-found the web hosting company "Schlund+Partner." The company "Schlund+Partner" later became the 1&1 web hosting product line. From 1995 to 2008, he was the technical director for several important projects: the largest web hosting platform in the world, the second largest DSL platform, a video on-demand delivery network, the largest eMail backend in Europe, and a universal billing syste...
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...
Containers are revolutionizing the way we deploy and maintain our infrastructures, but monitoring and troubleshooting in a containerized environment can still be painful and impractical. Understanding even basic resource usage is difficult - let alone tracking network connections or malicious activity. In his session at DevOps Summit, Gianluca Borello, Sr. Software Engineer at Sysdig, will cover the current state of the art for container monitoring and visibility, including pros / cons and li...
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively.
Somebody call the buzzword police: we have a serious case of microservices-washing in progress. The term “microservices-washing” is derived from “whitewashing,” meaning to hide some inconvenient truth with bluster and nonsense. We saw plenty of cloudwashing a few years ago, as vendors and enterprises alike pretended what they were doing was cloud, even though it wasn’t. Today, the hype around microservices has led to the same kind of obfuscation, as vendors and enterprise technologists alike ar...
The web app is agile. The REST API is agile. The testing and planning are agile. But alas, data infrastructures certainly are not. Once an application matures, changing the shape or indexing scheme of data often forces at best a top down planning exercise and at worst includes schema changes that force downtime. The time has come for a new approach that fundamentally advances the agility of distributed data infrastructures. Come learn about a new solution to the problems faced by software organ...
Saviynt Inc. has announced the availability of the next release of Saviynt for AWS. The comprehensive security and compliance solution provides a Command-and-Control center to gain visibility into risks in AWS, enforce real-time protection of critical workloads as well as data and automate access life-cycle governance. The solution enables AWS customers to meet their compliance mandates such as ITAR, SOX, PCI, etc. by including an extensive risk and controls library to detect known threats and b...
Docker is hot. However, as Docker container use spreads into more mature production pipelines, there can be issues about control of Docker images to ensure they are production-ready. Is a promotion-based model appropriate to control and track the flow of Docker images from development to production? In his session at DevOps Summit, Fred Simon, Co-founder and Chief Architect of JFrog, will demonstrate how to implement a promotion model for Docker images using a binary repository, and then show h...
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction....