Gatling

For Groupe IMA, performance testing is about more than technical metrics. When a driver calls for roadside assistance or an emergency signal is triggered from a vehicle, the systems behind those services need to respond quickly, reliably, and at any time. That’s why IMA introduced Gatling Enterprise Edition as part of a broader shift toward developer-driven performance testing. Instead of keeping load testing centralized, IMA is bringing it closer to the teams building and maintaining its applications. With Gatling, their teams can: ✅ Write simulations in Java, using skills developers already have ✅ Version performance tests alongside application code ✅ Trigger tests through CI before release candidates ✅ Validate both business applications and shared infrastructure components ✅ Detect scalability issues before they reach production In one case, a Gatling simulation revealed significant performance degradation in a geolocation-related application. The team identified the issue, implemented a fix, and confirmed stable results in a follow-up test before deployment. That’s the value of making performance testing part of the delivery workflow: issues are found earlier, fixes are validated faster, and reliability becomes a shared engineering responsibility. Great to see IMA turning load testing into a repeatable engineering habit with Gatling Enterprise Edition. If you want to learn more, a link to the full customer story is in the comments. #LoadTesting #PerformanceTesting #DevOps #SoftwareEngineering #TestAsCode #Gatling

Load tests tell you what happened in the last run. They don't tell you if your systems are getting better. Today we're releasing Campaigns and Scores, a new layer in Gatling Enterprise Edition that gives your performance testing program something it's never had: a point. Attach your tests to a business goal. Every run contributes to a score. Every score is snapshotted. Over time, you build the kind of evidence that makes go/no-go a decision you can defend, not a gut feeling you hope is right. The score tracks three things: → Methodology: are your tests configured with rigor? → Objectives: are your systems meeting their SLOs? → Confidence: is that performance consistent over time? Your engineers understand what drives it. Your leadership understands what it means. Check the link in the comments:

Gatling is heading to Datadog DASH 2026! If you're using Datadog to monitor your applications, come see what happens when you pair it with real load. Gatling injects controlled, repeatable traffic into your stack so Datadog can do what it does best: analyze, explain, and help you prevent performance issues before your users ever experience them. At DASH, we'll show how engineering teams are turning observability into continuous performance intelligence: spot bottlenecks under load, enforce performance gates in CI/CD, and get percentile-level insights that passive monitoring alone can't provide. Trusted by 300,000+ companies. Works with the tools you already use. Come find us at DASH 2026 and let's talk performance. 👋 #DASH2026 #Datadog #LoadTesting #PerformanceEngineering #Gatling

CFTL - Comité Français des Tests Logiciels's Journée Française des tests logiciels (JFTL) is one of the best places in the French-speaking world to talk about testing. Come find us at our booth if you want to: → See a live Gatling demo push an API past its limits → Get an honest answer to a performance problem you're stuck on → Understand what Gatling Enterprise adds for your team → Or just talk shop with people who care about this stuff See you there! #loadtesting #performancetesting #JFTL #Gatling

Finance teams don't just need pass/fail results from their load tests. They need metrics that reflect the actual realities of banking, trading, and fintech systems. We mapped out the 8 metrics that matter most, grouped by what they reveal: throughput and latency, errors and sessions, business flow duration, and network and infrastructure health. Each one comes with pro tips for financial services environments specifically. Link in the comments.

Early June brings two performance testing talks with one shared question: How much do you really know about how your application behaves under pressure? Heather Thacker, our Developer Advocate, will be speaking at two upcoming events in the US 🇺🇸 , covering two practical sides of performance testing for modern engineering teams. On June 2 at NashJS, she’ll present Node.js Under Pressure: Finding Your Breaking Point, a talk about discovering how much traffic your Node.js API can actually handle before users are the ones finding the limits for you. She’ll cover how to: - Establish performance baselines - Increase load systematically - Identify bottlenecks - Interpret meaningful metrics - Plan for growth with more confidence On June 6, at SREday New York, she’ll present Choose Your Weapon: The Performance Testing Arsenal, a practical breakdown of load testing, stress testing, soak testing, and spike testing. Because these tests sound similar, but they answer very different questions: can the app handle expected traffic? - Where does it break? - What happens after hours, days, or months of sustained use? - How does it react to sudden spikes? If you’re building, scaling, or operating web applications, both sessions are designed to make performance testing more approachable and easier to bring into your everyday workflow. See you there! #PerformanceTesting #LoadTesting #SRE #NodeJS #DevOps

Still running load tests in JMeter? Heather Thacker, our Developer Advocate is hosting a live demo on June 16 to show exactly how to convert JMeter test plans into Gatling simulations, including how our AI-powered tools can do it for you automatically. We'll cover: → How JMeter concepts map to Gatling → A live .jmx conversion, step by step → Common gotchas and how to handle them → AI-assisted migration + Enterprise deployment Whether you're evaluating Gatling, running both tools, or ready to make the switch, you'll leave with a clear, practical path forward. 🔗 The link to register is in the comments. If you can't make it that day, don't worry, you'll get the replay. #LoadTesting #PerformanceTesting #JMeter #Gatling #DevOps

Performance testing isn’t the same as performance maturity. Some teams test only when something breaks. Others validate before releases. A few use performance insights to guide real decisions. The difference comes down to maturity. We built a performance maturity assessment to help teams understand where they stand. It evaluates organizations across six pillars: Process Requirements Environment Automation Metrics Culture In about 4 minutes, you’ll get: • Your maturity stage • A breakdown of strengths and gaps • Recommendations tailored to your lowest-scoring areas The goal: help teams move toward Continuous Performance Intelligence — where performance becomes a strategic capability. Try it here: https://lnkd.in/eiFh2VhP

Performance testing used to be an engineering concern. DORA just made it a board-level one. Financial institutions are now required to demonstrate continuous, documented resilience — not assert it. A quarterly test report won't satisfy that standard. Neither will a monitoring dashboard that tells you what broke after it broke. We wrote this whitepaper for the leaders accountable for that gap. It covers how financial services organizations are moving from periodic testing to continuous performance governance — with SLOs that produce auditable compliance scores, load tests versioned like code, and trend data that gives regulators the evidence trail they're asking for. Including how EPI Company (backed by 16 major European banks) embedded performance testing into every release — and how Nickel (4.5M accounts, 20-30x traffic spikes) made it mandatory before every CAB review. The link to the whitepaper is in the comments!