
Gatling Enterprise Cloud
Automated API performance testing has streamlined workflows and now saves weeks of manual effort
What is our primary use case?
Gatling Enterprise is used by our organization to create performance test cases and functional test cases for our service. A specific example of one of the test cases we created using Gatling Enterprise is for a pricing service, which we built in Java, so we needed a Java-based testing service. Before we were using JMeter, but now we are moving to Gatling Enterprise.
How has it helped my organization?
Gatling Enterprise has positively impacted our organization by streamlining the workflow, easing the task, and reducing manual labor. In terms of hours saved, we have reduced approximately one to two weeks worth of work.
What is most valuable?
The best features Gatling Enterprise offers include being used in Java, providing a very good interface so we do not have to manually do the UI changes and can simply write the code. It is very much integrable with AI, and AI can write Gatling Enterprise scripts for us.
The AI integration has helped us significantly. We basically created a skill so that from the OpenAPI spec file, it can directly read the data and create the Gatling Enterprise script for us, so we do not have to manually code all the scripts.
Regarding Gatling Enterprise's AI capabilities, I believe it is pretty secure, and we did not find any issues working with it. Its accuracy and reliability of output seem pretty accurate and reliable, and we did not find any problems.
What needs improvement?
The setup is a little difficult. What I found is that you have to do a manual setup for Gatling Enterprise to be installed on your computer, and that can be improved.
For how long have I used the solution?
I have been using Gatling Enterprise for approximately six months.
What do I think about the stability of the solution?
Gatling Enterprise is stable.
What do I think about the scalability of the solution?
Gatling Enterprise's scalability is pretty scalable, and we did not find any issues.
How are customer service and support?
The customer support for Gatling Enterprise is good.
Which solution did I use previously and why did I switch?
We previously used JMeter, which was UI based and did not involve a lot of coding in it. However, as we are all developers here in Oracle, it is much easier for us to work with Gatling Enterprise.
How was the initial setup?
The setup is a little difficult. What I found is that you have to do a manual setup for Gatling Enterprise to be installed on your computer, and that can be improved.
What was our ROI?
I have seen a return on investment. In testing, our team's employment situation has improved in that fewer employees are needed, and we do not need a large number of workforce as before when we were using JMeter. We required a lot of QA staff, but now we do not.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing has been that it is free only. Gatling Enterprise is open source, and licensing requires a third-party license, but it is easy.
Which other solutions did I evaluate?
Before choosing Gatling Enterprise, we evaluated JMeter versus Gatling Enterprise and found Gatling Enterprise to be much better.
What other advice do I have?
If you are a small developer team, then it is good to have Gatling Enterprise for testing purposes. I found this interview good and do not believe anything needs to change for the future. My overall review rating for Gatling Enterprise is 8.
Rich Data Generators and Powerful Simulation Run Management
I also like the simulation run management and history offered by the enterprise product which lets non-engineers to access and use the results directly.
The technical documentation is an ever-evolving artifact but in its current state it is useful and well structured and helps newcomers create effective simulations, not just "hello world" versions.
Infrastructure budget projections
Identification of throughput bottlenecks
SLO monitoring
Performance regression
Seamless Integrations and Great Out-of-the-Box Reports
Gatling’s Fluent, Readable Test Scripting Is a Joy to Use
Highly Functional Tool for Performance Testing
Flexible Cloud Setup That Fits Every Team
First, it removes the ceiling we hit with local testing. When we run tests locally, we’re limited by how many users a workstation can handle, which is usually not enough to understand real scaling behavior (at least with Java; with Scala it’s much better). With Gatling Enterprise, we can safely push tests into the thousands of users and see how our systems actually behave under load.
Second, it gives us a controlled way to stress critical user paths so we can validate autoscaling and overall system stability. The biggest benefit isn’t the report itself, but the engineering signal: whether the service stays healthy, whether scaling kicks in correctly, and where it breaks as load increases.
With Gatling cloud, we also have the option to run tests from external networks or private IPs, which is great for validating the end-to-end user journey.
Gatling Enterprise API Streamlines Load Testing and Scheduling
We were able to build a command line tool to automate the simulation scheduling flow so that our developers could iterate fast.
A large-scale tool, easy to use and integrate into the testing cycle.
- Excellent (dynamic) reporting
- Support for different programming languages
- Easy-to-understand and learn documentation
- Open source with an easy-to-use injection platform
- Integration in CI/CD