Deep dives into event delivery, infrastructure patterns, and building reliable systems.
Two kinds of writing live here: Queuey engineering articles on event delivery, infrastructure patterns and building reliable systems — and Queuey comparison resources covering the webhook and event delivery platforms teams evaluate alongside Queuey.
Start with the comparison guide, Queuey vs the Alternatives, for the full architectural map: webhook platforms (Svix, Hookdeck, Hook0, Convoy), HTTP delivery (QStash, Webhook Relay), cloud event infrastructure (AWS EventBridge, Azure Event Grid), durable execution (Inngest, Temporal), Kafka, and building it yourself.
Event delivery often starts with an HTTP request and quietly grows into retries, queues, idempotency, DLQs and recovery logic. Why is this still application code?
A practical guide to reliability between the device, the edge and the cloud — offline operation, event custody, delayed telemetry and where MQTT's guarantees stop.
An AI agent can make the right decision and still create the wrong outcome. As agents reach production, AI reliability becomes a distributed systems problem.
During GitHub’s August 17 outage, a latent retry bug amplified traffic by approximately 10×. The interesting part isn’t that retries failed. It’s that the system kept retrying after retries had become part of the problem.
Every integration project quietly solves the same problems. The firms that stop rebuilding the same operational foundation will define the next category of integration consulting.
Why the Agentic Internet is fundamentally different from Web3—and why the next generation of software will be designed for agents first, humans second.