Files
jgrusewski d25c82f8f3 refactor: rename api_gateway → api across workspace, tests, and load crate
- Workspace Cargo.toml: remove web-gateway + api_gateway members, keep api
- trading_service: dep api-gateway → api, update test imports
- testing/api-gateway-load → testing/api-load (crate renamed)
- All test crates: get_api_gateway_addr → get_api_addr + variable renames

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-04 23:38:21 +01:00
..

api-gateway-load

Load testing framework for API Gateway with 4 scenarios: normal (1K clients), spike (10K ramp), sustained (24h), and stress (incremental to failure).

Key Types

  • TestOrchestrator -- scenario coordination
  • VirtualClientPool -- authenticated HTTP client generation
  • MetricsCollector -- HDR histogram latency tracking
  • ReportGenerator -- HTML + SVG chart output

Scenarios

  • normal -- 1K concurrent clients, 60s, target <10ms P99
  • spike -- 0 to 10K in 10s, sustain 60s
  • sustained -- 100 clients, 24h endurance
  • stress -- incremental increase until failure

Usage

cargo run --release -p api-gateway-load -- normal --gateway-url http://localhost:50050
cargo run --release -p api-gateway-load -- all --gateway-url http://localhost:50050