Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions versioned_docs/version-v2.0.0/architecture/overview.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 1
---

# Apache EventMesh Architecture

> **Audience:** anyone who wants the structural view — the three planes,
Expand Down Expand Up @@ -437,7 +433,7 @@ ingress path does not import legacy wire types.

## Documentation

The [documentation map](../documentation-map.md) organizes everything by audience. Highlights:
The [documentation map](../index.md) organizes everything by audience. Highlights:

| Page | What it covers |
| --- | --- |
Expand All @@ -454,4 +450,4 @@ The [documentation map](../documentation-map.md) organizes everything by audienc
| [Protocols & SDKs](../feature/protocols.md) | Wire protocol inventory and per-language SDK status |
| [Storage SPI](../feature/storage-spi.md) | `MeshStoragePlugin` contract and capability matrix |
| [Deployment](../feature/deployment.md) | Modes, Docker, multi-instance, runbooks |
| [Design records](../documentation-map.md#design-records-contributors) | Redesign rationale, evidence, plans |
| [Design records](../index.md#design-records-contributors) | Redesign rationale, evidence, plans |
14 changes: 5 additions & 9 deletions versioned_docs/version-v2.0.0/architecture/redesign.md
Original file line number Diff line number Diff line change
@@ -1,16 +1,12 @@
---
sidebar_position: 3
---

# EventMesh Architecture Simplification Redesign

> **Status note:** this is the historical design document for the
> architecture rewrite (a design record, not a living guide). The current
> implementation status and maturity of each capability are governed by the
> [capability status table](https://github.com/apache/eventmesh#capability-status) in the main
> [capability status table](../../README.md#capability-status) in the main
> README. For the user-facing views see
> [Architecture overview](overview.md) and the
> [feature guides](../feature/pubsub.md).
> [feature guides](../feature/).

> Branch: `refactor/unified-runtime-pipeline` — based on the direction
> defined in this document.
Expand Down Expand Up @@ -250,7 +246,7 @@ A single launcher (`EventMeshApplication`) starts traffic HTTP + admin (+
opt-in WebSocket). The deletion list removed the TCP/gRPC server paths,
`eventmesh-registry`, and dead modules (~59% of the tree). The phased plan
tracked the migration; the evidence trail lives in
[architecture review evidence](redesign.md).
[architecture review evidence](review/evidence.md).

---

Expand Down Expand Up @@ -401,7 +397,7 @@ routing was later covered by the sticky-instance model.)*

The end-to-end test-case design (§18) mapped every guarantee above to a
named test; the current test inventory and per-PR evidence live in
[review evidence](redesign.md).
[review evidence](review/evidence.md).

The streaming design (§20–21, integrated from the streaming-session,
sdk-streaming-call, and lite-streaming-call designs) defines the two
Expand All @@ -428,7 +424,7 @@ still-current content from those appendices lives in the feature and
reference pages of this documentation tree (configuration, protocols,
offset management, load balancing, frame protocol); the point-in-time
gap/migration tables are superseded by the
[architecture review evidence](redesign.md) and are intentionally
[architecture review evidence](review/evidence.md) and are intentionally
not reproduced.

*Document version: v2.0 (English rewrite of the Chinese original) ·
Expand Down
4 changes: 0 additions & 4 deletions versioned_docs/version-v2.0.0/architecture/security.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 2
---

# Security

**Audience:** operators and embedders securing an EventMesh deployment —
Expand Down
16 changes: 6 additions & 10 deletions versioned_docs/version-v2.0.0/documentation-map.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,4 @@
---
sidebar_position: 0.5
---

# Documentation Map
# Apache EventMesh Documentation

Welcome to the Apache EventMesh documentation. EventMesh is a **stateless
application-layer event mesh** for cloud-native, serverless, and AI-agent
Expand All @@ -12,7 +8,7 @@ subscription, offset, and delivery semantics itself — the broker is used
purely as a write-ahead log.

> Maturity tags (**GA / Beta / Experimental / Legacy**) for every capability
> live in the [capability status table](https://github.com/apache/eventmesh#capability-status) in the
> live in the [capability status table](../README.md#capability-status) in the
> project README — that table is the single source of truth.

## Where to start
Expand Down Expand Up @@ -52,9 +48,9 @@ too.
inside a parent topic; publish/poll semantics and checkpoints.
- [A2A — Agent-to-Agent](feature/a2a.md) — the agent collaboration protocol:
task lifecycle, JSON-RPC/MCP bridge, REST + SDK usage
*(Experimental)*; [readiness decision](feature/a2a-readiness.md).
*(Experimental)*.

- [Connectors](feature/connectors/connectors.md) — bridge EventMesh with external
- [Connectors](feature/connectors/README.md) — bridge EventMesh with external
systems (Kafka, RocketMQ, RabbitMQ, databases, chat platforms): the connector
model, running a worker, and a per-plugin guide for all 23 shipped plugins.

Expand Down Expand Up @@ -103,9 +99,9 @@ too.
- [Unified architecture redesign](architecture/redesign.md) — the original
rewrite design record (English rewrite): iron rules, target architecture,
decision log, semantics boundaries.
- [Architecture review evidence](architecture/redesign.md) —
- [Architecture review evidence](architecture/review/evidence.md) —
PR/test evidence behind every closed review issue.
- [Production HA acceptance plan](architecture/redesign.md)
- [Production HA acceptance plan](architecture/review/production-ha-plan.md)

## Conventions

Expand Down
118 changes: 0 additions & 118 deletions versioned_docs/version-v2.0.0/feature/a2a-readiness.md

This file was deleted.

23 changes: 9 additions & 14 deletions versioned_docs/version-v2.0.0/feature/a2a.md
Original file line number Diff line number Diff line change
@@ -1,26 +1,21 @@
---
sidebar_position: 5
---

# EventMesh A2A 协议(Agent-to-Agent Communication Protocol)
# EventMesh A2A Protocol (Agent-to-Agent Communication)

> **Audience:** builders of agent systems. The A2A wire contract, task
> lifecycle, and usage via REST / SDK. **Experimental** — see
> [readiness decision](a2a-readiness.md) for the promotion gates.
> lifecycle, and usage via REST / SDK. **Experimental**

---

---

## 目录
## Table of Contents

- [1. Overview](#1-overview)
- [2. Core Philosophy](#2-core-philosophy)
- [3. Architecture](#3-architecture)
- [4. Protocol Specification](#4-protocol-specification)
- [5. Implementation Summary](#实现总结eventmesh-a2a-协议-v20-mcp-版)
- [5. Implementation Summary](#5-implementation-summary)
- [6. Test Results](#test-results-eventmesh-a2a-protocol-v20)
- [7. 中文使用指南](#中文使用指南整合自-readmemd)
- [7. Usage Guide](#7-usage-guide-integrated-from-readmemd)

---

Expand Down Expand Up @@ -220,8 +215,8 @@ To support MCP on an Event Bus, synchronous RPC concepts are mapped to asynchron

| Concept | MCP / JSON-RPC | CloudEvent Mapping |
| :--- | :--- | :--- |
| **Action** | `method` (e.g., `tools/call`) | **Type**: `org.apache.eventmesh.a2a.tools.call.req`<br />**Extension**: `a2amethod` |
| **Correlation** | `id` (e.g., `req-123`) | **Extension**: `collaborationid` (on Response)<br />**ID**: Preserved on Request |
| **Action** | `method` (e.g., `tools/call`) | **Type**: `org.apache.eventmesh.a2a.tools.call.req`<br/>**Extension**: `a2amethod` |
| **Correlation** | `id` (e.g., `req-123`) | **Extension**: `collaborationid` (on Response)<br/>**ID**: Preserved on Request |
| **Direction** | Implicit (Request vs Result) | **Extension**: `mcptype` (`request` or `response`) |
| **P2P Routing** | `params._agentId` | **Extension**: `targetagent` |
| **Pub/Sub Topic** | `params._topic` | **Subject**: The topic value (e.g. `market.btc`) |
Expand Down Expand Up @@ -501,7 +496,7 @@ client.shutdown();
---


## 核心成果
## 5. Implementation Summary

A2A 协议已成功重构为采用 **MCP (Model Context Protocol)** 架构,将 EventMesh 定位为现代化的 **智能体协作总线 (Agent Collaboration Bus)**。

Expand Down Expand Up @@ -719,7 +714,7 @@ The A2A Protocol v2.0 implementation is stable, functionally complete, and ready

---

## 中文使用指南(整合自 README.md)
## 7. Usage Guide (integrated from README.md)

## 使用指南

Expand Down
4 changes: 0 additions & 4 deletions versioned_docs/version-v2.0.0/feature/admin-api.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 15
---

# Admin API Reference

**Audience:** operators and dashboards. Every endpoint below lives on the
Expand Down
4 changes: 0 additions & 4 deletions versioned_docs/version-v2.0.0/feature/architecture-guard.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 11
---

# EventMesh Architecture Guard

> Issue: #5305 (P0), #5322 (fail-mode), #5342 (Q7 expansion)
Expand Down
6 changes: 1 addition & 5 deletions versioned_docs/version-v2.0.0/feature/client-java.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 13
---

# Apache EventMesh Client Guide

> **Audience:** Java application developers using `eventmesh-sdk-java`
Expand Down Expand Up @@ -676,7 +672,7 @@ See also:

* [docs/architecture/overview.md](../architecture/overview.md) — system
architecture, control / data / agent planes
* [docs/index.md](../documentation-map.md) — feature-by-feature
* [docs/index.md](../index.md) — feature-by-feature
guide
* [docs/quickstart/configuration.md](../quickstart/configuration.md) — every
runtime key
Expand Down
4 changes: 0 additions & 4 deletions versioned_docs/version-v2.0.0/feature/connector-api-split.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 12
---

# Connector API split — design plan (P1)

**Status:** Plan only. No code in this PR. Implementation should land in a follow-up PR after
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"label": "Connectors",
"position": 6.5,
"position": 9,
"collapsed": true
}
4 changes: 0 additions & 4 deletions versioned_docs/version-v2.0.0/feature/connectors/canal.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 9
---

# Canal (MySQL CDC) connector

**Audience:** operators bridging EventMesh with Canal (MySQL CDC). MySQL change-data-capture via a deployed canal server. Source consumes binlog entries over the canal TCP protocol (batch ack only after EventMesh accepted the publish); sink replays row-change CloudEvents into a target MySQL as one all-or-nothing JDBC batch.
Expand Down
4 changes: 0 additions & 4 deletions versioned_docs/version-v2.0.0/feature/connectors/chatgpt.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 23
---

# ChatGPT (OpenAI) connector

**Audience:** operators bridging EventMesh with ChatGPT (OpenAI). OpenAI bridge. Source exposes an HTTP prompt endpoint: a client POSTs a prompt, the connector optionally completes it through the OpenAI REST API and emits both as a CloudEvent. Sink forwards events to a webhook (generic).
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 1
---

# Connectors

**Audience:** operators and developers wiring EventMesh to external systems —
Expand Down
4 changes: 0 additions & 4 deletions versioned_docs/version-v2.0.0/feature/connectors/dingtalk.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 18
---

# DingTalk connector

**Audience:** operators bridging EventMesh with DingTalk. DingTalk bridge. Source receives robot outgoing-callback messages (with HMAC signature verification); sink posts events to a DingTalk group-robot webhook.
Expand Down
4 changes: 0 additions & 4 deletions versioned_docs/version-v2.0.0/feature/connectors/file.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 12
---

# File connector

**Audience:** operators bridging EventMesh with File. Local file bridge — the simplest way to try connectors. Source reads a text file line by line; sink appends each CloudEvent as a line to a file.
Expand Down
4 changes: 0 additions & 4 deletions versioned_docs/version-v2.0.0/feature/connectors/http.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
---
sidebar_position: 16
---

# HTTP connector

**Audience:** operators bridging EventMesh with HTTP. Generic HTTP bridge. Source is a webhook receiver: any system can POST events into EventMesh without an SDK. Sink forwards each CloudEvent to an HTTP endpoint.
Expand Down
Loading
Loading