- 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>
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 coordinationVirtualClientPool-- authenticated HTTP client generationMetricsCollector-- HDR histogram latency trackingReportGenerator-- HTML + SVG chart output
Scenarios
normal-- 1K concurrent clients, 60s, target <10ms P99spike-- 0 to 10K in 10s, sustain 60ssustained-- 100 clients, 24h endurancestress-- 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