apache/eventmesh
EventMesh is a new generation serverless event middleware for building distributed event-driven applications. observed · 2026-08-28
Health v2 · maintenance only
75/100
- Activity 98
- Release rhythm 31
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: 372
- age_days: 2543
- days_rel: 246
- days_push: 13
- n_releases_24m: 2
Adoption not part of the score
1746 stars · 654 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Apache EventMesh is a cloud-native, serverless event middleware for building distributed event-driven applications. It provides a unified CloudEvents-based event bus with multi-protocol gateways (HTTP, gRPC, TCP, WebSocket), pluggable event stores like RocketMQ and Kafka, and a Serverless Workflow orchestration engine.
Use cases
- decouple microservices with a pub/sub event bus
- route events between services and external systems via CloudEvents
- build event-driven applications with at-least-once delivery guarantees
- orchestrate event workflows with declarative YAML
- bridge Kafka, RocketMQ, Pulsar, and RabbitMQ behind one gateway
- connect AI agents through a unified agent message bus
- translate between HTTP, gRPC, TCP, and WebSocket protocols
- manage event schemas across a distributed system
When to choose
- you need a vendor-neutral event backbone built on the CloudEvents standard
- you want to unify multiple message queues behind a single event gateway
- you need event routing, filtering, transformation, and workflow orchestration in one platform
- you are building multi-cloud or widely distributed event-driven topologies
- you want protocol translation between HTTP, gRPC, TCP, and WebSocket without code changes
When to avoid
- you only need simple point-to-point messaging that a single broker like Kafka or RabbitMQ already covers
- you want a lightweight in-process message bus inside a single application
- your team cannot operate an additional Java-based middleware layer
- you need strict exactly-once semantics in every scenario despite the advertised support
Facets
service · maturity active
message-queue middleware api-gateway workflow-automation webhook rpc http-server sdk microservices cloud-computing backend apis jvm cloud self-hosted cross-platform event-driven-architecture cloudevents event-mesh event-gateway event-streaming event-sourcing cqrs pubsub serverless-workflow esb event-connector a2a-protocol schema-registry messaging ai-agents docker kubernetes
10 sources
- readme: https://github.com/apache/eventmesh · fetched 2026-08-28 · bab6dfdd81a7
- homepage: https://eventmesh.apache.org/ · fetched 2026-08-29 · adf4ebe73d6d
- site_page: https://eventmesh.apache.org/docs/introduction · fetched 2026-08-29 · 2518bf3aff05
- site_page: https://eventmesh.apache.org/docs/next/introduction · fetched 2026-08-29 · 328c4bfba5b2
- site_page: https://eventmesh.apache.org/docs/v1.11.0/introduction · fetched 2026-08-29 · 9c9e18b97472
- site_page: https://eventmesh.apache.org/docs/v1.10.0/introduction · fetched 2026-08-29 · 32a79a8387cf
- site_page: https://eventmesh.apache.org/docs/v1.9.0/introduction · fetched 2026-08-29 · f69dc11cd01c
- site_page: https://eventmesh.apache.org/docs/v1.8.0/introduction · fetched 2026-08-29 · d73825bc52d3
- site_page: https://eventmesh.apache.org/docs/v1.7.0/introduction · fetched 2026-08-29 · f4138243cca0
- site_page: https://eventmesh.apache.org/docs/v1.6.0/introduction · fetched 2026-08-29 · 58e819484477
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| apache/eventmesh | main | 75 |
For agents
markdown · JSON · MCP: product_card(name="apache/eventmesh")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem