Book Image

Master Apache JMeter - From Load Testing to DevOps

By : Antonio Gomes Rodrigues, Bruno Demion (Milamber), Philippe Mouawad
Book Image

Master Apache JMeter - From Load Testing to DevOps

By: Antonio Gomes Rodrigues, Bruno Demion (Milamber), Philippe Mouawad

Overview of this book

Load tests help identify the maximum number of requests a software system can handle. One popular open source tool for load testing is JMeter. By leveraging the features and capabilities of JMeter, you can perform extensive load testing and fix issues in your application before they become problematic. This book is written by JMeter developers and begins by discussing the whole process, including recording a script, setting it up, and launching it, enabling you to almost immediately start load testing. You'll learn the best practices that you must follow while designing test cases. You'll also explore the different protocols offered by JMeter through various real-world examples. Finally, you'll see how to integrate JMeter into the DevOps approach and create professional reports. You'll discover ways to use the eco-system of JMeter to integrate new protocols, enrich its monitoring, and leverage its power through the use of the cloud. By the end of this book, you'll know all that's needed to perform comprehensive load testing on your applications by using all the best practices and features of JMeter.
Table of Contents (14 chapters)

A Bit of Theory

As architectures become more and more distributed (via microservices, the cloud, and so on), it is common to use a Message-Oriented Middleware (MOM) service to allow the exchange of messages/events.

Such architectures have numerous advantages. We'll look at some of them in this lesson.

Asynchronous Messages

The first advantage of an MOM service is the ability to use asynchronous messages.

In a synchronous system, the sender (that is, the producer) of the message must wait for the response before continuing:

Figure 10.1: Synchronous architecture

In an asynchronous system, however, the producer of the message can continue their processing after sending the message without waiting for a response from the receiver:

Figure 10.2: Asynchronous architecture

In asynchronous mode, the MOM will act as an intermediary and store the message until it is delivered to Application 2.

Decoupling

This proxy role allows for weak coupling between the different entities...