Speak at Bengaluru Systems meet-up

Abstract

An event mesh’s core strength is rerouting around failure without static config - a broker goes down, routes repropagate, traffic finds a new path. A conventional service tolerates the rough edges of that failover with idempotency keys and dedup; it gets a duplicate, shrugs, moves on. An autonomous AI agent downstream of the same failover doesn’t get to shrug - a duplicate means it acts on the same signal twice, with no idea it already responded. Same failover, different blast radius.

This talk takes that one scenario - broker failure and route repropagation and replays it for a service and for an agent sitting on the other end, to show exactly where the guarantee holds and where it quietly runs out.

Key takeaway:

Event mesh guarantees were built for services that fail loudly. Agents fail quietly, inside their own reasoning - which raises the bar for what the mesh has to promise.

Speaker Bio

https://www.linkedin.com/in/girivenkatesan/