Under sustained load, misconfigured connection pools silently exhaust all available connections. Requests start queuing, timeouts cascade, and the entire service goes down — often with misleading error messages that point away from the actual cause.
This scenario should demonstrate connection exhaustion with an undersized pool and no statement timeout, then show how proper HikariCP sizing + statement_timeout prevents cascading failures.
Strategies to compare:
- Undersized pool with no timeout (baseline — reproduces exhaustion)
- Right-sized pool based on the connection pool sizing formula
- Pool + statement timeout as a safety net
- Pool metrics/monitoring to catch problems early
k6 load test should ramp connections beyond pool capacity. Proof: baseline causes connection wait timeouts; fixed config sustains throughput. Follows PRD acceptance criteria AC-1 through AC-5.
Under sustained load, misconfigured connection pools silently exhaust all available connections. Requests start queuing, timeouts cascade, and the entire service goes down — often with misleading error messages that point away from the actual cause.
This scenario should demonstrate connection exhaustion with an undersized pool and no statement timeout, then show how proper HikariCP sizing +
statement_timeoutprevents cascading failures.Strategies to compare:
k6 load test should ramp connections beyond pool capacity. Proof: baseline causes connection wait timeouts; fixed config sustains throughput. Follows PRD acceptance criteria AC-1 through AC-5.