For thirty years the web has had exactly one safe way to ask a server a question — GET — and it can't carry a body. So every real search endpoint quietly cheats with POST and loses caching, idempotency, and honesty about what it's doing. QUERY is the proposed method that fixes the thirty-year-old workaround: safe and idempotent like GET, but with a request body like POST.
A five-step order flow dies after step three: the card is charged, the stock is held, and the process that knew what came next is gone. Sagas, outboxes, and idempotency keys are how we've survived that crash for a decade — by hand-building a state machine every single time. Durable execution flips the model: write the flow as straight-line code, and let an engine replay it back to the exact line where it died.
There is a way to run your own code inside the Linux kernel — attached to a syscall, a network packet, a function entry — without writing a kernel module and without rebooting. That sounds like it should be impossible or insane, and it's neither. It's eBPF, and it's quietly become the foundation under nearly every observability, networking, and security tool you already use.
Both slogans read the same — your code runs on demand, no server to manage. But one runs a full Node.js box in a single far-away data center, and the other runs a stripped-down V8 isolate a few milliseconds from your user. The difference between them is where they run and what they're allowed to do, and that difference decides which one belongs on your request path.
HTTP/3 didn't invent new headers or smarter routing — it kept HTTP exactly the same and swapped the pipe underneath. Instead of TCP plus TLS, it runs on QUIC over UDP, and that one change fixes head-of-line blocking, cuts the handshake to a single round trip, and lets a connection survive you walking from Wi-Fi to cellular.
SQL injection was killed by a structural fix: parameterized queries drew a hard line between code and data. Prompt injection is the same shape of bug with no such line — for an LLM, instructions and data arrive in one channel, and nothing reliably marks 'this part is data, never obey it.' Here's why agents make it lethal, and how to design as if injection will succeed.