Backpressure and slow-consumer handling

Write apps/backend/docs/concepts-backpressure.md for services/backpressure.ts: how per-socket buffer occupancy is monitored, the shed and disconnect thresholds, and what happens to a client that cannot keep up.

Acceptance criteria:

Documents both tiers with their env-configurable thresholds and current defaults
States accurately which tier actually changes emit behaviour today and which is currently only tracked — a reader must not infer protection that is not wired in
Explains the client-visible effect of a hard disconnect and how resume recovers from it
Cross-links the resume/replay mechanism

@hardeyshorlar12

@hardeyshorlar12 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, assign this to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @hardeyshorlar12 to this issue.

@Joeljosef7

@Joeljosef7 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'd like to claim this issue. I can document the backpressure system, including buffer monitoring, shed/disconnect thresholds, configurable defaults, and the actual client behavior of each tier.

I'll also explain hard disconnect recovery and cross-link the existing resume/replay mechanism, keeping the documentation accurate to the current implementation.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Joeljosef7 to this issue.

@johdanike

@johdanike has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I can pick this up! I will write concepts-backpressure.md to clearly explain the socket buffer monitoring, shed, and disconnect thresholds. I'll make sure the distinction between the actively enforced and currently tracked protection tiers is explicitly stated, alongside the client recovery and replay mechanisms. Building and documenting robust, high-concurrency systems is a core part of my backend engineering workflow. Happy to be assigned!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @johdanike to this issue.

@johdanike

Congratulations, @johdanike! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @johdanike: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

@Mikardo001

@Mikardo001 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hey, please assign, i can fix this very fast

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mikardo001 to this issue.

@josephchimebuka

@josephchimebuka has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi GM, I have reviewed this issue and taken the time to understand the requirements, current implementation, and the expected outcome. Based on my analysis, I believe this is something I can successfully handle and contribute to... Kindly assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @josephchimebuka to this issue.

@josephchimebuka

Congratulations, @josephchimebuka! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @josephchimebuka: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

docs: add backend concept pages and ADR index for codebestia#550 code…

Addressed in #610 (retargeted to dev after #609 was auto-closed for targeting main).

Closed by #610, merged into dev.

@josephchimebuka

This issue has been completed by @josephchimebuka as part of the Stellar Wave Program's 9th Wave 🥳

😎 @josephchimebuka: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Navigation Menu

Repository navigation

Backpressure and slow-consumer handling #559

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Backpressure and slow-consumer handling #559

Description

Activity

hardeyshorlar12 commented on Aug 31, 2026

Joeljosef7 commented on Aug 31, 2026

johdanike commented on Aug 31, 2026

drips-wave commented on Aug 31, 2026

Mikardo001 commented on Sep 26, 2026

josephchimebuka commented on Sep 28, 2026

drips-wave commented on Sep 28, 2026

josephchimebuka commented on Sep 29, 2026

github-actions commented on Sep 29, 2026

drips-wave commented on Sep 29, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions