Why Event-Driven · Broker vs HTTP
13 / 14
The Coordination Problem Agents Actually Have

A message broker solves this structurally. Solace has done it for 20+ years.

Synchronous HTTP
Fragile at Agent Scale
Connections held open for minutes waiting on LLM turns and slow tool calls
Retry logic reimplemented at every layer in application code
Any network partition anywhere in the chain loses the task
Calling agent blocks. If either side restarts, delegation is lost.
vs
Message Broker Solace
Designed for This
Publisher sends and moves on. Subscriber receives when ready. No blocked connections.
Delivery guarantees are a broker property, not application code every team reimplements
Checkpointing: ACK on durable state write. Another instance resumes if one crashes.
20+ years in financial trading, logistics, and industrial IoT. Task loss has consequences there.
Decouple send from receive. Let the broker handle coordination.