Serverless & Edge
-
Cold Starts Are Not the Problem With Serverless
Cold start latency is measurable, bounded, and largely solved. The genuine serverless difficulties are connection management, local testing, and cost…
Read More » -
Cache Invalidation Is Hard Because You Are Doing It Wrong
Purging caches when content changes is fighting the architecture. Immutable URLs with content hashes eliminate invalidation entirely for most assets.
Read More » -
Serverless Portability Claims Rarely Survive Contact With a Real Migration
A function handler looks portable in isolation. The event source format, the IAM binding and the deployment tooling around it…
Read More » -
HTTP/3 Fixes a Problem TCP Could Never Actually Solve
A single lost packet in an HTTP/2 connection stalls every request multiplexed onto it, because TCP guarantees ordered delivery across…
Read More » -
Edge Functions Are a Different Runtime, Not a Smaller One
Code written for a full serverless function frequently fails to run at the edge, not because the edge is less…
Read More » -
Cache Invalidation Fails Quietly When It Relies on Time Alone
A time-to-live setting is a guess about how long content stays valid, and it is either too short to save…
Read More »
