Learn how LoadStrike approaches distributed load testing with coordinator and agent roles plus NATS-backed execution.
LoadStrike handles distributed load through coordinator and agent patterns that let the test stay one workload even when execution spans more than one node. The public docs also describe NATS-backed distributed execution for teams that need a broader self-hosted load footprint.
That matters when a single host is not enough for the workload, the scenario needs environment-specific placement, or the team wants one transaction-aware runtime across multiple execution nodes.
Teams that need multi-node execution for scale, placement, or operational realism while keeping one transaction-aware report surface.
Single-host runs can stop being representative when the workload needs more traffic sources, more browser capacity, or explicit coordination between roles. Endpoint-only tools also tend to make multi-node orchestration a separate concern from the transaction model itself.
LoadStrike publishes cluster overview, coordinator-and-agent, NATS-backed distributed execution, and targeting docs so the cluster shape, scenario selection, and self-hosted rollout controls stay visible in the public documentation.
These pages cover the public clustered-execution story in LoadStrike.
Start with the high-level cluster model.
See the core coordinator/agent pattern.
Target the right scenarios to the right roles.
Review NATS as part of the public distributed story.
These questions are rendered on the page and mirrored in the matching FAQ structured data when the route is indexable.
Yes. The public docs include cluster overview and coordinator-and-agent pages that explain how the distributed execution model is framed on the site today.
Yes. The public materials describe NATS-backed distributed execution and also document a NATS endpoint guide for teams already working with NATS in the workload itself.
Open the cluster overview, coordinator-and-agent, and node-targeting docs first, then connect that reading back to the workload pages for microservices, event-driven, or browser-aware testing.
Keep moving from positioning into concrete product detail.
Cluster mode lets one LoadStrike run spread across multiple nodes. Use it when a single machine is not enough or when topology matters.
Learn how coordinator and agent nodes split, execute, and merge one clustered LoadStrike run.
Node targeting decides which scenarios stay on the coordinator and which are pushed to agents in clustered runs.
Use these routes when the next question is tool choice rather than implementation detail.
Compare LoadStrike and Apache JMeter across scenario design, protocol coverage, downstream correlation, browser workflows, reporting, and self-hosted operations.
Compare LoadStrike and Gatling across scenario discipline, request modeling, downstream visibility, transport breadth, reporting depth, and self-hosted operations.
These reporting pages connect the transaction model to the observability systems already documented publicly.
See how the LoadStrike TimescaleDB sink fits into transaction-aware reporting workflows and public Grafana starter assets.
See how the LoadStrike Grafana Loki sink fits into transaction-aware reporting and public Grafana starter assets.
Every published route should help you move to the next concrete question instead of ending in a dead end.
See how the deployment model fits multi-node programs.
Connect distributed execution back to service-heavy workloads.
Review how future benchmark pages should describe topology and artifacts.
Open the quick start, map the transaction you already care about, and keep the workflow explicit from source action to downstream completion.
