Engineering notes, field guides and perspectives on reliable event delivery.
Engineering notes, field guides and perspectives on reliable event delivery, organized around event delivery, AI and agents, IoT and edge systems, integrations, and comparisons.
Start with a featured guide, browse by topic, or compare Queuey with webhook platforms, cloud queues and building delivery infrastructure yourself.
The Guide to the IoT Galaxy — 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.
The Agent Worked. The System Failed. — 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.
From fish welfare to export logistics, seafood's next digital challenge is not simply collecting more information. It is knowing who controls it, what it means and whether it actually arrives.
Microsoft and GitLab experienced restart loops just three weeks apart. Here's how automated health checks prolonged the outages, and why this isn't just a Kubernetes problem.
Coding agents are making first versions dramatically cheaper to build. That may also mean companies end up owning far more internal software than they ever consciously decided to.
Replay needs payload retention. Data minimization pushes the other way. Here’s how to separate delivery history, payload retention and access without giving up reliability.
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.