Limit upstream connections per service without unbounded waiting
A slow upstream creates an unlimited queue behind a finite connection pool.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Backpressure
Estimated field mix
- Networking50%
- Performance engineering30%
- Site reliability20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional reporting API sits behind a reverse proxy. Clients see intermittent disconnects and incorrect origins after changes to keep-alive and forwarding headers.
Setup prerequisites
- Create two loopback HTTP services and a local proxy with synthetic requests; no public scanning or external traffic.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Set finite active and waiting limits.
- Return explicit overload responses when waiting is full.
- Remove cancelled waiters.
Implementation constraints
- Keep limits service-scoped and observable.
Verification to include
- Serve within the configured pool.
- Overflow the wait queue and verify no resource leak.
Deliverables
- Bounded upstream pool.
Rollout and recovery
Start conservatively; tune only from recorded workload behavior.
Value of the work
For the engineer: Practice HTTP intermediaries, connection lifetimes, and network failure isolation.
For the team: Provide a proxy contract that preserves request identity and releases resources predictably.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.