Gatling Enterprise Cloud

What do you like best about the product?

It’s easy to record network traffic, which makes it great for back-end performance testing. It can also be integrated with real-time data display tools like Grafana. Easy for implementing in a remote server and for daily load testing. Written in Java code, it allows users to implement highly complex user scenarios. Having the free tier version to begin. Newly AI integration. Supporters are highly available.

What do you dislike about the product?

Having fewer useful features in the free tier version than the enterprise version.

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

Gatling allows our company to define the load capacity and security capacity of our services with less cost and easy maintenance.

What do you like best about the product?

I like Gatling because it allows for simple and efficient load testing. I have used it in my work to validate application performance in both non-production and production environments, analyzing metrics and detecting bottlenecks to identify improvement opportunities.

What do you dislike about the product?

One of its main limitations is that it has a steeper learning curve than tools like JMeter, especially due to its code-based approach. Additionally, it can be more complex to simulate complete scenarios and highly varied or dynamic user flows, requiring more effort to model them accurately.

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

Gatling allows for the detection of performance issues before they reach production, such as bottlenecks, high response times, or degradation under load. It benefits me because I can validate application capacity and detect problems early.

What do you like best about the product?

I like Gatling because it provides a scalable performance testing framework that's easy to maintain. The reporting is great, and I appreciate the reusability options for scenarios, which makes testing more efficient. It integrates well across CI/CD pipelines and the initial setup was a breeze. Switching from JMeter to Gatling was smooth due to the user-friendly framework and code.

What do you dislike about the product?

The documentation could be improved. I'd like to see more examples, especially around authentication, data parameterization, and assertions, as it would make onboarding easier.

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

Gatling provides a scalable performance testing framework for our CI/CD pipelines. It's easy to maintain and offers proper reporting and scenarios reusability, making it a great tool for performance testing.

What do you like best about the product?

It’s simple to use, and it lets me design tests that follow a real user journey.

What do you dislike about the product?

Some features are only available in the Enterprise version, while others are genuinely interesting and useful.

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

I’m able to design tests at both large and small scales, and the architecture lets me adapt quickly in either direction.

What do you like best about the product?

Gatling's Java DSL is the standout feature — writing load test scenarios in code means tests live in Git, get peer-reviewed, and stay maintainable long-term. We built a shared internal library (gatlingcommon) of reusable feeders, load patterns, and helpers that any team can import and use in minutes, which has dramatically reduced onboarding time for new load test projects.

The built-in HTML reports are clean and actionable — per-request percentile breakdowns, throughput charts, and response time distributions are generated out of the box with zero dashboard setup, cutting post-run analysis time significantly.

CI/CD integration is seamless — the Maven plugin fits naturally into Jenkins pipelines, giving fine-grained control over simulation execution and report generation.

Performance-wise, Gatling is exceptionally efficient. A single node can simulate thousands of virtual users with minimal resource consumption.

Pricing is a strong ROI story for open-source users — the core tool is free, and the ecosystem is mature enough to cover most enterprise load testing needs.

The community forum is active, and the documentation is thorough. Onboarding a new team member to write their first simulation takes a day, not a week.

What do you dislike about the product?

The biggest limitation is distributed load testing: the open-source version offers no supported way to merge binary simulation logs from multiple nodes into a single consolidated report. Starting with Gatling 3.11.x, the simulation log format changed to binary, which makes manual log merging impossible. In 3.10.x, manually merging logs was a workable workaround, but that option is no longer available. As a result, teams running distributed tests are pushed to either stay on older versions or move to Gatling Enterprise.

Support for the open-source version is community-driven only. When you hit critical blockers, the official response is often along the lines of, “this is only supported in Gatling Enterprise.”

Reference: https://community.gatling.io/t/generate-gatling-report-from-multiple-simulation-log-files-with-version-3-13-5/9737

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

Gatling solves the problem of realistic, high-volume load testing in a developer-friendly way. By providing a code-first DSL in Java, it allows us to write load test scenarios that are version-controlled, peer-reviewed, and reusable — treating performance tests as first-class code rather than throwaway scripts.

The biggest benefit has been standardization across teams. We built a shared internal library of reusable load patterns, feeders, and helpers that any team can import, which means a new load test project can be up and running in minutes instead of days.

Gatling also solves the reporting problem — generating detailed HTML reports with per-request percentile breakdowns, throughput, and response time distributions out of the box means we spend less time building dashboards and more time acting on results.

On the CI/CD side, the Maven plugin integrates cleanly into Jenkins pipelines, making it easy to run performance tests as part of our regular release process rather than as a manual afterthought.

Overall, Gatling has shifted load testing from a specialist activity to something any developer on our team can contribute to.

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.