Task library BPROXY
Project scope 10 tickets / 3 phases
Total focused work estimate 27h + setup
Suggested stack TypeScript · HTTP · Local reverse proxy Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with BPROXY-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice HTTP intermediaries, connection lifetimes, and network failure isolation.
What the team gains Provide a proxy contract that preserves request identity and releases resources predictably.
Before you start Create two loopback HTTP services and a local proxy with synthetic requests; no public scanning or external traffic. Delivery agreement Deliver a local proxy configuration or adapter plus reproducible failure checks.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Constrain forwarding and request interpretation.
PHASE 2 Handle reuse, timeouts, and cancellation.
PHASE 3 Measure behavior and rehearse configuration recovery.
Define proxy trust Constrain forwarding and request interpretation.
BPROXY-101 Entry ticket; project setup still required BPROXY-102 Depends on BPROXY-101 BPROXY-103 Depends on BPROXY-102 Estimated field mix
Networking 80% API design 20% Manage connections Handle reuse, timeouts, and cancellation.
BPROXY-104 Depends on BPROXY-103 Estimated field mix
Networking 60% Performance engineering 40% BPROXY-105 Depends on BPROXY-104 Estimated field mix
Networking 50% Performance engineering 30% Site reliability 20% BPROXY-106 Depends on BPROXY-105 Estimated field mix
Networking 50% Backend 30% Performance engineering 20% BPROXY-107 Depends on BPROXY-104, BPROXY-106 Estimated field mix
Networking 40% API design 30% Distributed systems 30% Verify proxy changes Measure behavior and rehearse configuration recovery.
BPROXY-108 Depends on BPROXY-105, BPROXY-106, BPROXY-107 Estimated field mix
Performance engineering 60% Networking 40% BPROXY-109 Depends on BPROXY-108 Estimated field mix
Networking 60% Site reliability 40% BPROXY-110 Depends on BPROXY-109 Estimated field mix
Site reliability 50% Networking 50% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.