Need Event Destinations as the Agent Backbone, Not Just HTTP
At meaningful agentic scale, agents and humans should be guided to durable-queue event destinations — SQS, EventBridge, Pub/Sub, Kafka, RabbitMQ — not HTTP-only delivery, because the producer / consumer pie shifts when agents are producing events at machine pace.
Take Control Of Your Signals — Become a Naftiko Design Partner Today!
Persona Story:
Nico is watching event-driven architecture get reframed in real time. HTTP-based event delivery solves the bottom of the market — most enterprise event needs are basic. But at meaningful agentic scale, where agents both produce and consume events at machine pace, durable-queue destinations (SQS, EventBridge, Pub/Sub, Kafka, RabbitMQ) become the right backbone. Outbound webhook engines that deliver directly into customers’ queues already exist; what is missing is the architectural framing that says this is where the agent web actually lives.
Problem Context
- HTTP-based events solve most enterprise scenarios — practitioners agree that “good documentation, good communication, and HTTP” covers a lot of EDA work
- At significant agentic scale, every event matters and back-pressure / durability matter, which pushes the architecture toward durable queues
- Event-destinations as a category (Stripe, Shopify, ex-Twilio product alumni all citing it) is rising; reference implementations are starting to ship
- The agent producer / consumer pie shifts when agents are producing at machine pace — the consumer side gets bigger and the durability requirements get sharper
Problem Impact
- HTTP-only architectures cannot keep up with agent-generated event volume and lose messages under load
- Customers route agent events through ad hoc webhook chains that they then have to monitor and patch
- The agent web’s reliability ceiling is set by whichever layer is HTTP-only
- Integration leads cannot tell when to recommend HTTP versus when to recommend durable queues because the framing is missing
Naftiko Today
- Executable YAML capability specs can declare both HTTP and event-destination consume / expose surfaces, so a capability can carry either backbone without rewrites
- MCP exposure layer (Streamable HTTP, stdio) covers the synchronous side while leaving the asynchronous side open to durable backbones
- outputParameters with JSONPath, field renaming, and nested-object support normalize event payloads so consumers see consistent shapes regardless of upstream backbone
- External bindings keep queue endpoints, credentials, and topic names configurable so the same capability moves between HTTP and durable backbones cleanly
Naftiko Tomorrow
- Webhook adapter (Second Alpha) will give capabilities a first-class outbound webhook + event-destination surface so durable delivery is built in, not bolted on
- A2A (Agent-to-Agent) adapter (Second Alpha) will define how agent-to-agent event flows traverse durable backbones reliably
- Tool annotations (Second Alpha) will let capabilities declare delivery semantics so consumers can choose HTTP versus durable queues with eyes open
- Fabric capability discovery (v1.1) will surface event-backbone characteristics across the fabric so architects can route by reliability and cost