Gatling Enterprise Cloud

What do you like best about the product?

I like best about Gatling is its code-first approach to performance testing. Test scenarios are written as maintainable code, which makes them easier to review, version, refactor, and integrate into a regular development workflow.

What do you dislike about the product?

the initial learning curve. The DSL is elegant once you understand it, but engineers without experience in Scala or functional programming concepts may find the syntax and error messages less approachable than JMeter’s graphical interface. Also we need more steps to set everything up to work with Scala. However, it is possible to choose Kotlin or Java instead.

What problems is the product solving and how is that benefiting you?

Gatling solves the problem of creating maintainable and repeatable performance tests for APIs and web applications. It allows performance scenarios, workload models, test data, checks, and assertions to be defined as code and stored together with the application or test project.

Compared with GUI-based tools such as JMeter, Gatling makes collaboration through Git more practical. Changes are easier to review, merge, and track, especially when the performance test suite becomes larger and more complex.

It is possible to execute Gatling from Ci CD pipelines and collect the results automatically

What do you like best about the product?

Its really good tool for load testing tool i actually use it for my old legacy app and it really helped me to improve the app performance.

What do you dislike about the product?

It’s difficult for an end user to understand the UI, so it could be improved in that area to make it clearer and easier to use.

What problems is the product solving and how is that benefiting you?

We were struggling with performance issues in our app. Since the app was live and a legacy application, we were dealing with production issues on a daily basis. To address all of that, we decided to go with Gatling.

What do you like best about the product?

I like that Gatling is a non-GUI, developer-centric tool. The fact that scripts can even be AI-generated is pretty cool, and I find the memory footprint per script to be actually minuscule. It's efficient enough that I can use a single VM to run over 500 threads. I also appreciate how Gatling can be integrated into our dev workflows, allowing Claude to auto-generate Gatling scripts as we develop and build APIs. Additionally, AI can go through Postman collections to create a complete Gatling suite of scripts. Setting up Gatling was rather easy, with no problems there.

What do you dislike about the product?

Since Gatling is non-GUI, I find it has a learning curve for us non-developers. It takes time for us to figure out the functions and features. Also, I face challenges because Gatling requires Scala, and I had to cross-train Java developers to read and understand Scala code.

What problems is the product solving and how is that benefiting you?

I use Gatling for scripting end-to-end business workflows, creating reusable templates, and scaling our performance testing frameworks. The low memory footprint allows running 500+ threads on a single VM. It integrates with our dev workflows for auto-generating scripts.

What do you like best about the product?

What I like most about Gatling is how easy it is to create and maintain performance tests. As an automation tester, I find its code-based approach more flexible than record-and-playback tools. It integrates smoothly with CI/CD pipelines, generates clear and detailed reports, and helps identify performance issues quickly. Overall, it's a reliable tool that makes performance testing efficient and fits well into modern automation workflows.

What do you dislike about the product?

One thing I dislike about Gatling is that it has a bit of a learning curve, especially if you're new to Scala or its scripting syntax. Creating complex test scenarios can take more effort compared to some GUI-based tools. Also, debugging scripts isn't always straightforward, and some advanced features require extra setup. That said, once you're familiar with it, the flexibility and performance make it worth using.

What problems is the product solving and how is that benefiting you?

Gatling helps us identify performance bottlenecks before applications go live by simulating real user traffic and measuring how the system behaves under load. As an automation tester, it gives me confidence that new features can handle expected traffic without affecting performance. It also helps catch issues early in the development cycle, supports continuous testing through CI/CD integration, and provides detailed reports that make it easier to analyze results and share insights with the team.

What do you like best about the product?

What I like most about Gatling is its flexibility and the ability to build complex performance test scenarios as code. It gives me full control over test flows, dynamic data, request generation, and different load injection models.

I particularly appreciate that Gatling can be extended beyond standard HTTP testing. In my case, I use it for complex SOAP-based scenarios with dynamic request generation, WS-Security signing, custom mock services, and multi-step transaction flows. The Java-based DSL also makes it easier to structure, maintain, and reuse test components compared to traditional GUI-based performance testing tools.

Another strong point is the clear separation between test logic, request generation, and load profiles, which makes the test project easier to develop and integrate into CI/CD pipelines.

What do you dislike about the product?

There is not much I dislike about Gatling itself. One challenge is that more complex or non-standard use cases can require additional custom development and a deeper understanding of the underlying technologies. For example, working with SOAP, WS-Security, or custom mock services requires building some functionality yourself.

However, this is also a consequence of Gatling's flexibility, as it gives you the freedom to implement scenarios that go beyond typical HTTP/REST performance testing.

What problems is the product solving and how is that benefiting you?

Gatling helps us validate the performance and stability of our systems under different load conditions before changes reach production. It allows us to simulate realistic, multi-step transaction flows and control how the load is generated, from gradual ramp-up to sustained concurrency and peak-load scenarios.

The main benefit is repeatability and automation. Performance tests can be maintained as code, reused across different scenarios, and integrated into CI/CD processes. This makes it easier to identify performance bottlenecks, compare system behavior between releases, and reproduce specific load conditions when investigating performance issues.

What do you like best about the product?

I used Gatling for load testing REST APIs in one of my projects. I find it very lightweight, which makes handling concurrency from a single machine much easier. Compared to tools like JMeter, Gatling consumes fewer resources, which is beneficial for simulating millions of users, like during a Black Friday sale, saving a chunk of money on resources. It's developer-friendly, which I appreciate since version control with development is easy. I also like its reporting features, especially the graphical representations, as they provide a clear view of performance metrics.

What do you dislike about the product?

I find it challenging to learn Scala, which can be quite difficult for new folks who need to invest a lot of time. I feel Gatling's free tier is less flexible compared to open-source tools like JMeter that give you more ease to scale in the way you want. Setting up the Scala environment was somewhat difficult.

What problems is the product solving and how is that benefiting you?

I use Gatling for its lightweight and developer-friendly nature, which eases handling high concurrency with less infrastructure. It's valuable for cost-effective load testing, especially with its graphical reporting that enhances insights.

What do you like best about the product?

What I like best about Gatling is its ability to simulate realistic user loads and provide detailed performance metrics. Being code-based, it allows test scripts to be version-controlled and integrated easily into CI/CD pipelines. I also appreciate its rich reports and dashboards, which help quickly identify performance bottlenecks and analyze system behavior under load.

What do you dislike about the product?

What I dislike about Gatling is that it is less beginner-friendly than GUI-based performance testing tools. Since it is code-centric, it requires programming knowledge and can take more effort to create, debug, and maintain complex test scenarios.

What problems is the product solving and how is that benefiting you?

Gatling solves the challenge of validating an application's performance, scalability, and stability under different user loads before issues impact production. It helps identify bottlenecks such as slow response times, resource constraints, and throughput limitations by simulating realistic user traffic.
For me, the main benefit is the ability to proactively detect performance issues early in the development lifecycle. This helps improve application reliability, supports performance validation in CI/CD pipelines, and provides valuable insights through detailed reports, enabling teams to deliver a better user experience and reduce production risks.

What do you like best about the product?

The ability to customize the validations and the ability to integrate as a DSL in different programming languages. The broad community is fundamental when it comes to select it since you can find solutions to most of challanges from people in the past already.

What do you dislike about the product?

The HTML report is hard to modify; we have to depend on a cloud solution, which, for a small project, is not feasible.

What problems is the product solving and how is that benefiting you?

Ability to customize and create so detailed validations during performance testing, and the ability to incorporate additional programming dependencies to enrich your validation. When it comes to E2E performance testing, we can find so many flavours in user flows, and those features of Gatling give you the ability to adapt the tool to so many user flows and technologies

What do you like best about the product?

I like that Gatling is lightweight and easy to use. There are many options available for script preparation, which allows us to work fast and achieve accurate results. The initial setup was smooth, making it easier for us to transition to using Gatling for performance testing activities.

What do you dislike about the product?

We have an issue with the report file not being generated in Excel format. Instead, Gatling reports are provided in a different file format. It would be better if Gatling could generate reports in Excel format as well.

What problems is the product solving and how is that benefiting you?

I use Gatling for performance testing to solve production issues. It's lightweight and easy to use, with many script options. We work fast and get accurate results.

What do you like best about the product?

I found Gatling easy to understand and write code in. Even when I joined the project without knowing anything about Gatling, the inbuilt repository with the code and framework was easy to comprehend. The code is in a very readable format, so anyone with some technical knowledge can read, understand, and write it. The documentation on the Gatling site is pretty self-explanatory, making it straightforward to learn anything new and implement Gatling code in services. Working with Gatling was really good because of this easy-to-read and follow documentation. The initial setup was also easy, with top-notch documentation that anyone can follow.

What do you dislike about the product?

Not anything to say at this stage

What problems is the product solving and how is that benefiting you?

I use Gatling for performance testing. It's easy to understand and write code, even for newcomers. The documentation is self-explanatory, aiding quick setup and implementation.