Skip to content

M9-08 Performance & Load Testing

Milestone: M9 — Hardening and Compliance SOW Reference: NFR1 Requirement Clarity: ✅ Clear Dev Status: ❌ Not started — no load-testing tooling or results exist anywhere in the repo today

Overview

Validate the platform meets the NFR1 performance targets: 1000-2000 transactions/hour, 1000 concurrent users, 100 registration requests/minute, sub-2-second response times at peak load.

Backend Tasks

  • Choose a load-testing tool (k6, Artillery, Locust, etc.)
  • Write load-test scenarios covering issuance, disclosure, and verification flows
  • Run against a production-like environment and capture results

Frontend Tasks

  • N/A

Dependencies

  • Needs M2-M8 functionality substantially complete to test realistically.
  • M4-01 AWS hosting decision — load test environment should match production infra.

Acceptance Criteria

  • Load test report demonstrates compliance (per SOW Appendix 3, Performance Testing)

Existing Reference Material

None — this is genuinely new work, not represented anywhere in the current docs.

Blockers & Risks

  • Risk: if left until late in M9, there may not be enough runway to fix performance issues found. Consider an early, partial load test against M4's release rather than waiting for everything to be built.