* docs(cloud-computing): add dedicated roadmap links to related nodes
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs(cloud-computing): add network engineer roadmap link to networking basics
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs(cloud-computing): add roadmap.sh guides to related nodes
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Tighten the comparison and add what receivers need to handle in practice:
at-least-once and out-of-order delivery, signature verification (HMAC with
a shared secret), acknowledging quickly and processing in the background,
deduplicating by event ID, and combining webhooks with polling to catch
missed events.
Add the Standard Webhooks spec and GitHub's webhook best-practice and
signature-validation guides as resources.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The topic said idempotency "sometimes" applies to POST but did not explain
how. Clarify which HTTP methods are idempotent by definition and describe
idempotency keys, the common way to make POST/PATCH safe to retry:
client-generated unique key, stored result replayed on repeats, reuse with
a different payload rejected, keys expire.
Add MDN, the IETF Idempotency-Key header draft and Stripe's reference
implementation as resources.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Rewrite the topic copy to reflect current practice: retry only transient
failures (timeouts, 429, 502-504), cap retries, use exponential backoff
with jitter, respect Retry-After, and retry only idempotent requests.
The old copy suggested retrying until a request succeeds, which can cause
retry storms.
Add three resources on backoff, jitter and Retry-After. No other topic in
the API Design, Backend or AI Engineer roadmaps covers these yet.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Remove the 272 daily.dev "Explore top posts about ..." feed links
from 274 topic files across all roadmaps.
Three links were tagged @feed@ but are regular resources, so they
are retagged instead of removed:
- computer-science/sql-vs-nosql-databases: roadmap.sh guide -> @article@
- backend-beginner/git: YouTube crash course -> @video@
- game-developer/unreal-engine: Unreal Source Discord -> @article@
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
A repo-wide scan found 34 resource lines that link to an identical URL
as another line in the same file. Most look like content-sync artifacts
where a refreshed resource was appended but the stale one was never
removed; three were created by my earlier link fixes folding a dead URL
into an identical live one (cloudflare calls, cloudflare service
bindings, kotlinlang flow).
In each file the first occurrence is kept and only the later duplicate
is removed; no URLs or labels were modified.
Co-authored-by: Weijian He <230282609+Madin-H23@users.noreply.github.com>
Live fixes (8 links, 8 files):
- chakra-ui: /docs/getting-started removed, updated to the docs hub
- LanceDB: /enterprise/introduction folded into the /enterprise section
- openclaw docs: five deep links into moved /index pages updated to the
canonical paths (gateway/security, cli)
Dropped 8 resource lines whose sources are gone with no replacement
(all 404-verified twice): arbitrum get-started, harness kubernetes
blue-green guide (2 files), smartbear microservices (2 files),
userfrosting DI container article, AWS effective_cache_size tuning
page, inspirednonsense context engineering post.
All replacement URLs verified to resolve (HTTP 200).
Co-authored-by: Weijian He <230282609+Madin-H23@users.noreply.github.com>
