Gatling started as an open-source project in 2012 by Stéphane Landelle, while he was the chief technology officer (CTO) of a French IT consulting firm, eBusiness Information. In 2015 a dedicated company named "Gatling Corp" to develop a commercial product for load test orchestration and collaboration. The first version of Gatling Enterprise (originally named FrontLine) was released in 2016.

The company is based in Bagneux, France, near Paris.

Gatling Corp is a member of Systematic Paris-Region, an Île-de-France business cluster created in 2005,^[5] devoted to complex systems and ICT.^[6] Systematic Paris-Region gathers large groups, SMEs, universities and research labs to promote digital innovation. Gatling is a member of Systematic's Open Source Working Group and was elected member of Systematic's board of directors, as a representative of SMEs, in November 2016.

The company took part in some events, like the Paris Open Source Summit (POSS, 2015, 2016 and 2017 editions), Liferay's 2016 Symposium, Java User Group (JUG)'s meetings, the Paris Gatling User Group and the New York Gatling User Group.

Gatling consists of an open-source core and an enterprise orchestration and collaboration platform. The open-source performance testing tool includes:

• The high-performance load generator engine
• SDKs in multiple programming languages for Java, Scala, Kotlin, JavaScript, and TypeScript.
• Static HTML reports

Gatling Enterprise includes all of the open-source features and additionally:

• Real-time and interactive reporting
• Customized reports and sharing options
• Multiple load generator options, from fully managed to self-hosted
• Full CI/CD integration
• RBAC and SSO

• Simulation: The simulation file includes the different scenarios of a test, its parametrization and the injection profiles. Technically speaking, a simulation is a Scala class.^[7] Here are examples of simulations in Java and JavaScript:^[8][9]

//Java

public class BasicSimulation extends Simulation {

  HttpProtocolBuilder httpProtocol =
    http.baseUrl("https://e-comm.gatling.io")
      .acceptHeader("application/json")
      .contentTypeHeader("application/json");

  ScenarioBuilder myFirstScenario = scenario("My First Scenario")
    .exec(http("Request 1")
      .get("/session/"));

  {
    setUp(
      myFirstScenario.injectOpen(constantUsersPerSec(2).during(60))
    ).protocols(httpProtocol);
  }
}

//JavaScript

export default simulation((setUp) => {

  const httpProtocol =
    http.baseUrl("https://e-comm.gatling.io")
      .acceptHeader("application/json")
      .contentTypeHeader("application/json");

  const myScenario = scenario("My Scenario")
    .exec(http("Request 1")
      .get("/session/"));

  setUp(
    myScenario.injectOpen(constantUsersPerSec(2).during(60))
  ).protocols(httpProtocol);
});

• Scenario: A scenario consists of a series of requests. Each scenario within a simulation can have its own injection profile.^[10] Here is an example of a scenario:^[8][9]

//Java

ScenarioBuilder myFirstScenario = scenario("My First Scenario")
    .exec(http("Request 1")
      .get("/session/"));

  {
    setUp(
      myFirstScenario.injectOpen(constantUsersPerSec(2).during(60))
    ).protocols(httpProtocol);
  }

//JavaScript

const myScenario = scenario("My Scenario")
    .exec(http("Request 1")
      .get("/session/"));

  setUp(
    myScenario.injectOpen(constantUsersPerSec(2).during(60))
  ).protocols(httpProtocol);
});

• Group: Groups can be used as a subdivision of a scenario. It is also a series of requests, that has a functional purpose (for instance, the login process).
• Request: Gatling is able to simulate complex users' behaviors. For this purpose, it generates the appropriate requests in the system under test. Here is an example of a request in Gatling:^[8][9]

//Java

.exec(http("Request 1")
    .get("/session/"));

//JavaScript
.exec(http("Request 1")
      .get("/session/"));

• Injection profile: An injection profile is the number of virtual users injected during the test in the system under test and how they are injected. Here is an example of an injection profile:^[8]

//Java

    setUp(
      myFirstScenario.injectOpen(constantUsersPerSec(2).during(60))
    ).protocols(httpProtocol);

//JavaScript
setUp(
    myScenario.injectOpen(constantUsersPerSec(2).during(60))
  ).protocols(httpProtocol);

Gatling implemented a fully new architecture for a performance testing tool, in order to be more resource efficient.^[11] It makes it possible to simulate a high number of requests per second with a single machine.^[12]

It officially supports the following protocols:

• HTTP
• WebSockets
• Server-sent events
• JMS
• MQTT
• gRPC

Gatling documentation states that it is protocol agnostic, which makes it possible to implement other protocols' support.^[19]

Gatling comes out with official and community plugins. It integrates with:

• Integrated development environments (IDE), like Eclipse and IntelliJ IDEA
• Build automation software, or Build tools, like Apache Maven, Gradle, Npm and sbt
• Continuous Integration solutions like Jenkins, GitHub Actions, GitLab, TeamCity, and Bamboo

Automation with Gatling is related to its simulations' maintainability.^[21] The integration with other developer tools, especially in the DevOps lifecycle, makes it possible to create performance tests at scale, that is to say to fully automate the execution of performance testing campaigns in the software development process.

Gatling is published under Apache License 2.0,^[23] a permissive free software license written by the Apache Software Foundation (ASF).^[24]

The source code is accessible on GitHub.

Gatling Enterprise is the commercial version of Gatling. It is proprietary software, distributed by Gatling Corp.

• Apache JMeter
• LoadRunner
• Web server benchmarking
• Software performance testing
• Performance engineering
• Software testing
• Selenium (software)