Start with one request step, then go deeper.

LoadStrike docs are organized around what a team needs to do next: install the SDK, run a first request-step scenario, understand when the workload becomes a transaction, read the report, and scale into distributed execution when the workload demands it.

Docs pages 57

Guides, concepts, reference, reports, protocols, and operations coverage.

Groups 8

Organized by the job the reader is trying to complete next.

SDKs 6

Code tabs stay aligned across C#, Go, Java, Python, TypeScript, and JavaScript.

Start here

Follow the shortest path into a real result.

Most new teams only need four pages before the product model clicks.

Choose your SDK

Select a language once. The docs store that preference and reuse it across the code-tabbed pages.

Go uses module loadstrike.com/sdk/go. The website serves the vanity-import metadata for that path, so go get and pkg.go.dev resolve the public Go SDK automatically. Install the module, provide a valid runner key, and run workloads directly from Go.

One mental model across SDKs

Language-specific differences stay visible, but the same scenario, step, tracking, and reporting workflow carries through the docs.

Example request-step scenario

using LoadStrike;

var httpClient = new HttpClient
{
    BaseAddress = new Uri("https://api.example.com")
};

var scenario = LoadStrikeScenario.Create("read-order", async context =>
{
    var orderId = $"ord-{context.InvocationNumber}";

    var step = await LoadStrikeStep.Run<string>("GET /orders/{id}", context, async () =>
    {
        using var response = await httpClient.GetAsync($"/orders/{orderId}");

        return response.IsSuccessStatusCode
            ? LoadStrikeResponse.Ok<string>(statusCode: ((int)response.StatusCode).ToString())
            : LoadStrikeResponse.Fail<string>(
                statusCode: ((int)response.StatusCode).ToString(),
                message: "Order lookup failed");
    });

    return step.AsReply();
})
.WithLoadSimulations(
    LoadStrikeSimulation.Inject(10, TimeSpan.FromSeconds(1), TimeSpan.FromSeconds(20))
);

LoadStrikeRunner.RegisterScenarios(scenario)
    .WithRunnerKey("rkl_your_local_runner_key")
    .Run();

Read the docs in this order

Install

Pick the package and confirm the supported runtime for your SDK.

Quick start

Build one request-step scenario and run it with a valid runner key.

Concepts

Use the concept pages when the team needs to move from one request step into a full transaction definition.

Reports and cluster

Go deeper only after the first result is already working.

Browse by user need

Start here

Get from install to a first runnable request-step result without reading the whole reference surface.

Getting Started

3 pages

Concepts

3 pages

Library Options

14 pages

Configuration

7 pages

Reports

12 pages

Endpoints

8 pages

Cluster

6 pages

Protocols

4 pages