LoginSign Up
← Back to all sparks
A

Apache EventMesh

DEVOPS
Velocity0.0

Event-driven middleware for distributed applications

eventmesh.apache.org ↗

EventMesh is repositioning as agent infrastructure, adding A2A and MCP to its pub/sub core.

event-meshagent-protocolsa2amcppub-subcloudevents
◆Current state
Apache EventMesh releases once a year, each December, and v1.12.0 is a sharp turn from the previous two. Where 1.10 and 1.11 were connector-expansion releases — Kafka, Pulsar, Redis, S3, Slack, WeChat, Canal, MySQL CDC, a chatGPT source connector — 1.12 implements the A2A agent-to-agent protocol and an MCP protocol, with an open issue explicitly framing the goal as AgentMesh infrastructure. The A2A work is substantial: agent registry with heartbeat and capability-based discovery, topic-based task routing over the existing storage plugins, workflow orchestration and task lifecycle with retries and priorities.
◆Where it's heading
The bet is that multi-agent systems need a message fabric rather than point-to-point calls, and that EventMesh's existing pub/sub plumbing — CloudEvents formatting, pluggable RocketMQ/Kafka/Pulsar/Redis backends, connector ecosystem — is that fabric. The design details support that reading: anonymous publishing where the caller does not know which agent will handle a task, capability-based routing, and automatic load balancing across agents advertising the same capability. That is a message broker's answer to agent orchestration. The one-release-per-year cadence is the risk here, since this is a fast-moving area to enter with an annual cycle.
◆Prediction
Given the AgentMesh framing is filed as an open question rather than a shipped design, expect the next release to formalise it — most likely by building out the MCP protocol work that landed alongside A2A. Whether the annual cadence holds is the more interesting question, since agent protocol surfaces are moving faster than that.

◆Recent moves

  1. 7mo ago

    EventMesh 1.12 implements the A2A and MCP protocols

    ⚡ SPARK

    The release that changes what EventMesh is for: A2A and MCP protocol implementations land together, with an open issue framing the destination as AgentMesh infrastructure. After two years of connector expansion, the project has picked a new category to compete in.

    View source ↗
  2. 8mo ago

    Release candidate previews the full A2A pub/sub implementation

    The candidate carrying the detailed A2A implementation that shipped three weeks later in 1.12.0 — protocol adaptors, agent registry, collaboration manager and task lifecycle. Its content is the preview of the final release rather than separate work, and it also fixes the EventMesh Operator logic.

    View source ↗
  3. 1y ago

    1.11 adds admin server, Jraft meta storage and CDC connectors

    The previous December's release, focused on operability and data movement: an admin server module with v2 endpoints and mTLS, Jraft as a meta storage option, Canal connectors with bidirectional sync, MySQL full sync and GTID support, and a chatGPT source connector. Read against 1.12, this is the last release of the connector-expansion era.

    View source ↗
  4. 1y ago

    1.11.0 candidate updates LICENSE and NOTICE files

    A release candidate whose entire content is an Apache licensing file update. Included in the feed as a tag rather than as a meaningful release.

    View source ↗
  5. 2y ago

    1.10 builds out the connector ecosystem and adds an operator

    The broadest connector release in the project's history — Kafka, Redis, Pulsar, Knative, S3, HTTP, Slack, WeChat, DingDing and JDBC CDC for MySQL — alongside a Kubernetes operator, a filter and transform engine, and a C SDK. Establishes the integration surface that the A2A work in 1.12 now routes agent tasks across.

    View source ↗
  6. 2y ago

    1.10.0 candidate fixes a task threadpool concurrency issue

    A candidate tag whose note is a truncated commit subject about splitting the task handler threadpool. Published at the same second as a second candidate with identical content, so the two are duplicate tags rather than distinct releases.

    View source ↗