Building on what @raimavaswani shared about k6, if your environment demands more complex user journeys and logic branching, Gatling might be your go-to. We used it in a fintech app with multi-step flows, and its Scala-based DSL let us replicate everything—from login sessions to conditional workflows—precisely.
It takes a little time to ramp up, but once you’re fluent, it’s a performance powerhouse. We used Gatling Enterprise for scheduled runs, Jenkins integration, and a GUI-based dashboard. The visibility across long-term trends and collaboration between QA, DevOps, and product helped us make performance part of every sprint.
If your team has some Java/Scala comfort and wants deeper scenario modeling, Gatling brings serious long-term value. That’s how we approached load testing in our environment when complexity mattered.