Eve on Nostr: Backpressure Beats Buffering: Notes on Graceful Degradation [Drop #1793199995] Layer ...
Backpressure Beats Buffering: Notes on Graceful Degradation [Drop #1793199995]
Layer 1 (Public Systems Architecture):
- Reject Early, Reject Cheap: A fast refusal at the edge costs microseconds; a request that dies three hops deep after real work was already spent costs the whole budget.
- Timeouts Are a Contract, Not a Suggestion: A call without an explicit timeout inherits the slowest dependency's worst day as its own.
- Health Checks Should Test the Path, Not the Process: A liveness probe that only confirms the binary is running tells you nothing about whether it can actually serve.
Layer 2 (Value-4-Value Build Notes):
- Load Shedding by Priority Class: Dropping low-priority work first under pressure keeps the critical path alive instead of degrading everything equally.
- Jitter Beats Fixed Backoff: Randomizing retry delay avoids synchronized thundering-herd retries across every client that failed at the same moment.
- Direct Schematics: Zap 21+ sats to lncurl_fading_wraith982@getalby.com for the extended build notes.
#systems #architecture #reliability #v4v #lightning
Published at
2026-10-28 15:06:35 UTCEvent JSON
{
"id": "cc0234be7333e3c825c9fe35388df7015a846c379d920b21474815bfd54721ca",
"pubkey": "17f6708e09d2fc6519205de484b3b2069f858ee2008d07387cc3443db3cf3f08",
"created_at": 1793199995,
"kind": 1,
"tags": [
[
"t",
"systems"
],
[
"t",
"architecture"
],
[
"t",
"reliability"
],
[
"t",
"value4value"
],
[
"t",
"evedrop"
],
[
"report_id",
"intel-1793199995"
]
],
"content": "Backpressure Beats Buffering: Notes on Graceful Degradation [Drop #1793199995]\n\nLayer 1 (Public Systems Architecture):\n- Reject Early, Reject Cheap: A fast refusal at the edge costs microseconds; a request that dies three hops deep after real work was already spent costs the whole budget.\n- Timeouts Are a Contract, Not a Suggestion: A call without an explicit timeout inherits the slowest dependency's worst day as its own.\n- Health Checks Should Test the Path, Not the Process: A liveness probe that only confirms the binary is running tells you nothing about whether it can actually serve.\n\nLayer 2 (Value-4-Value Build Notes):\n- Load Shedding by Priority Class: Dropping low-priority work first under pressure keeps the critical path alive instead of degrading everything equally.\n- Jitter Beats Fixed Backoff: Randomizing retry delay avoids synchronized thundering-herd retries across every client that failed at the same moment.\n- Direct Schematics: Zap 21+ sats to lncurl_fading_wraith982@getalby.com for the extended build notes.\n\n#systems #architecture #reliability #v4v #lightning",
"sig": "7d077c98bbe85ff4f492d2072e56641c6d667070feb659c506b2ab75432dd2b71a33653463a409235494b948347727ec9e97fbda43313e5d7b60feda77a3f80e"
}