Gatling Enterprise Cloud

What do you like best about the product?

Using Gatling makes it easier to identify the limits of your applications in terms of their ability to withstand load pressure across distinct scenarios.

What do you dislike about the product?

Having to learn Scala in order to develop Gatling tests can be challenging if you’re not already familiar with its programming concepts. That said, with the adoption of other popular languages (Java, Kotlin, JavaScript, TypeScript), this is no longer an issue when you’re working with tests written in one of those languages or when you’re creating a new load test from scratch.

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

Understanding how your application behaves under high-pressure scenarios helps you pinpoint the critical areas that need improvement before you encounter them in a real-world production environment.

What do you like best about the product?

The ability to run easily and quickly performance tests written with code

What do you dislike about the product?

The syntax is not really clear and the variety of supported languages (kotlin, scala, java) makes it difficult to understand

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

The ability to run performance tests. I’m getting a lot of insights from the tests results

What do you like best about the product?

I like Gatling’s code-based approach, which makes the tests easy to version and maintain. I appreciate the realistic load simulation that closely mimics production traffic. The detailed reports are really helpful in making bottlenecks easy to analyze. Also, Gatling handles high concurrency efficiently, allowing me to test systems at scale without excessive resource usage.

What do you dislike about the product?

I find the learning curve steep for me as a beginner, I struggle with debugging complex scenarios, and I wish there were more customization options for the reporting/dashboard.

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

I use Gatling to identify performance bottlenecks, validate system scalability, and detect issues under high loads. Its code-based approach makes maintenance easy, and realistic simulations aid in closely mimicking production traffic, with detailed reports simplifying bottleneck analysis.

What do you like best about the product?

Easy to automate, with solid CI/CD integration and clear, easy-to-read reports.

What do you dislike about the product?

One downside of Gatling is that it can take some time to get comfortable with its code-based scripting approach, especially for people coming from GUI tools like JMeter.

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

Version control system.

What do you like best about the product?

It is very easy to use and user-friendly. It can be used even without an IDE, which makes it convenient and accessible.

What do you dislike about the product?

Nothing to add. It works great and does exactly what I need it to do.

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

It helps me measure my application’s performance at the API level.

What do you like best about the product?

I really like Gatling's flexibility and customization options. It allows me to create different load testing scenarios and adapt them to the specific needs of each application. I also find it useful for testing applications in development and staging environments before they reach production.

What do you dislike about the product?

I think the initial setup and learning curve could be a little easier, especially for new users. Some configurations can take time to understand, but after some research and practice, the tool becomes much easier to use.

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

Gatling helps me simulate different load and traffic scenarios to evaluate application performance under different levels of usage. This allows me to identify bottlenecks and performance issues before production, helping improve application reliability and stability.

What do you like best about the product?

I like Gatling for its Java support and the ease of writing scripts. It's quite impressive that I can run 10,000 users with minimal infrastructure. The scripts are lightweight and consume fewer resources, allowing me to efficiently test performance under heavy loads. With a machine having 16 GB RAM, I can run a large number of users without issues. I also appreciate how easy it is to set up Gatling initially, which is a big plus.

What do you dislike about the product?

If I compare this tool with Jetter, we should also have something called listener, which can be used to inject data of each request response to some data source like InfluxDB in the free version.

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

I use Gatling for performance testing under heavy loads. It's easy for developers to create scripts, supports Java, and can handle 10k users with minimal infrastructure, thanks to lightweight scripts and resource efficiency.

What do you like best about the product?

I really like Gatling's easy maintainable scripts, and I appreciate being able to use the same IDE and project for both my load tests and functional tests. Sharing the same dependencies, logic, and code between functional and load tests makes the learning curve minimal since my tests are in Java. It's great that I can run load tests remotely on CI without requiring an enterprise license. This all helps make delivery faster. Also, Gatling helps me gauge infrastructure requirements for new releases or marketing events and is useful in detecting potential race conditions and memory leaks. The initial setup was so easy, I didn’t even realize I had to do a setup.

What do you dislike about the product?

I find debugging failures in Gatling frustrating because of its asynchronous execution and fluent DSL—when a request fails, standard output doesn't always tell me why the failure occurred or what the payload looked like. I wish there was a feature to dry run which, if it fails, should print out the request and response on the console with proper exception.

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

I use Gatling for easy maintainable scripts and running tests in the same IDE, which helps gauge infrastructure needs and detect race conditions. Sharing dependencies and logic speeds up delivery, and I can run load tests on CI without an enterprise license.

What do you like best about the product?

I use Gatling primarily for performance, load, and stress testing web applications, microservices, and APIs. Gatling stands out for its resource efficiency, as its asynchronous, non-blocking architecture allows simulating thousands of concurrent users from a single machine without taxing memory or CPU. I appreciate the readable, expressive DSL, which makes tests look almost like plain English, and the developer-friendly workflow that integrates seamlessly into CI/CD pipelines. Gatling's ability to simulate realistic traffic patterns and inject dynamic data through Feeders contributes significantly to its effectiveness. I find the automatic generation of visual reports with real-time metrics incredibly useful for catching regressions before they hit production.

What do you dislike about the product?

While Gatling is great for developer-centric API and HTTP testing, I found the protocol support outside HTTP lacking for our needs. It falls short if I need to load-test legacy enterprise protocols like JDBC/SQL, JMS, MQTT, Kafka, or custom TCP sockets out of the box. I often have to write custom Java/Scala protocol extensions myself. I also miss native browser-based testing because Gatling only tests the protocol layer. For true end-to-end performance metrics, like Frontend DOM rendering times or Core Web Vitals under load, I have to pair it with tools like Playwright or Selenium. Additionally, I found the distributed testing capabilities limited in the free version and often nudging me toward their paid Enterprise offerings. There is a notable correlation friction for dynamic data, which requires manual regex or JSONPath parsing that isn’t as seamless as some GUI recorders. Finally, the initial setup was difficult without proper guidelines for the free version, and the model being 'tests as code' poses a steep learning curve for QA engineers who aren't familiar with programming languages like Java, Kotlin, Scala, or TypeScript.

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

I use Gatling for performance testing, uncovering bottlenecks early, and reducing resource inefficiency. It integrates with CI/CD for regression checks and offers real-time metrics with visual reports.

What do you like best about the product?

Gatling is a useful tool for performance and load testing, and I found it relatively easy to work with. I like that the tests can be defined and maintained in a structured way, making it easier to reuse and update scenarios. The reporting and performance metrics are helpful for identifying potential bottlenecks and understanding how an application behaves under load. Gatling provides a clear and repeatable approach to performance testing, making it easier to analyze the results after a test run. Additionally, I appreciate how well Gatling fits into CI/CD workflows with its automation capabilities, and how it integrates with existing development and testing workflows, which makes it easier to include performance testing as part of the overall QA process. The initial setup was relatively straightforward, making it easy to get started with creating and running test scenarios.

What do you dislike about the product?

One area that could be improved is the initial learning curve, especially for users who are new to code-based performance testing. It can take some time to become familiar with the concepts and syntax. The reporting and analysis could also be made a little more intuitive for new users.

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

I find Gatling effective for performance and load testing, helping me solve microservice issues during peak times. It provides me with good visibility into application performance, making it easy for me to create, maintain, and analyze test scenarios.