When a page is created
Backend & software
Separate pages built ahead of time from responses generated by application code, and see why static pages can still be interactive.
- comparison
Static vs dynamic website
Static pages can still be interactive. The key distinction is when and where HTML is produced for a request.
Explore the idea - concept
REST APIs and HTTP methods
HTTP methods express intended request semantics. Safe and idempotent are different properties; neither promises success, and method names alone do not certify a correct or RESTful implementation.
Explore the idea - comparison
Authentication vs authorization
Authentication establishes an identity; authorization decides whether it may perform a particular action on a resource. Being signed in does not supply a missing permission.
Explore the idea - comparison
Sessions vs JWT authentication state
A server session uses a lookup for state; a signed JWT can carry locally checked claims. A local-only verifier cannot learn an uncommunicated revocation, so invalidation is a key design tradeoff.
Explore the idea - concept
API rate limiting and HTTP 429
HTTP 429 indicates that the server has rate-limited the request. Use the provider’s limit and retry guidance to decide whether and when to retry; waiting alone does not establish that another attempt is safe or will succeed.
Explore the idea - procedure
Webhooks, retries and idempotency
Repeated webhook delivery must not duplicate business effects. An idempotent operation or correctly committed deduplication can help; reconcile an uncertain prior outcome before another non-idempotent change.
Explore the idea - comparison
Background job queues vs synchronous requests
A queue separates accepting work from completing it. Use it when results can arrive later with tracked outcomes; keep required immediate results synchronous. A queue does not add worker capacity.
Explore the idea
The static vs dynamic comparison follows where HTML is produced, not whether the browser runs JavaScript.