EventMesh is a dynamic event-driven application runtime used to decouple the application and backend middleware layer, which supports a wide range of use cases that encompass complex multi-cloud, widely distributed topologies using diverse technology stacks.
Apache EventMesh is a new generation serverless event middleware for building distributed event-driven applications.
Apache EventMesh has a vast amount of features to help users achieve their goals. Let us share with you some of the key features EventMesh has to offer:
Please go to the roadmap to get the release history and new features of Apache EventMesh.
This section of the guide will show you the steps to deploy EventMesh from Local, Docker, K8s.
This section guides the launch of EventMesh according to the default configuration, if you need more detailed EventMesh deployment steps, please visit the EventMesh official document.
Use the following command line to download the latest version of EventMesh:
sudo docker pull apache/eventmesh:latest
Use the following command to start the EventMesh container:
sudo docker run -d --name eventmesh -p 10000:10000 -p 10105:10105 -p 10205:10205 -p 10106:10106 -t apache/eventmesh:latest
Creating a topic is the first step in using EventMesh. You need to send an HTTP POST request to create a topic.
Example Request
POST /eventmesh/topic/create HTTP/1.1
Host: localhost:10105
Content-Type: application/json
{
"topic": "example-topic"
}
After creating a topic, you can subscribe to it to receive messages. EventMesh provides two subscription methods: local subscription and remote subscription.
POST /eventmesh/subscribe/local HTTP/1.1
Host: localhost:10105
Content-Type: application/json
{
"url": "http://localhost:8080/callback",
"consumerGroup": "example-consumer-group",
"topic": [
{
"topic": "example-topic",
"mode": "CLUSTERING",
"type": "SYNC"
}
]
}
EventMesh provides multiple message sending methods, including asynchronous sending, synchronous sending, and batch sending.
POST /eventmesh/publish HTTP/1.1
Host: localhost:10105
Content-Type: application/json
eventmesh-message-topic: example-topic
{
"content": "Hello, EventMesh!"
}
When you no longer need to receive messages for a topic, you can unsubscribe.
POST /eventmesh/unsubscribe/local HTTP/1.1
Host: localhost:10105
Content-Type: application/json
{
"url": "http://localhost:8080/callback",
"consumerGroup": "example-consumer-group",
"topics": ["example-topic"]
}
Each contributor has played an important role in promoting the robust development of Apache EventMesh. We sincerely appreciate all contributors who have contributed code and documents.
Apache EventMesh enriches the CNCF Cloud Native Landscape.
Apache EventMesh is licensed under the Apache License, Version 2.0.
WeChat Assistant | WeChat Public Account | Slack |
---|---|---|
![]() |
![]() |
Join Slack Chat(Please open an issue if this link is expired) |
Bi-weekly meeting : #Tencent meeting : 346-6926-0133
Bi-weekly meeting record : bilibili
Name | Description | Subscribe | Unsubscribe | Archive |
---|---|---|---|---|
Users | User discussion | Subscribe | Unsubscribe | Mail Archives |
Development | Development discussion (Design Documents, Issues, etc.) | Subscribe | Unsubscribe | Mail Archives |
Commits | Commits to related repositories | Subscribe | Unsubscribe | Mail Archives |
Issues | Issues or PRs comments and reviews | Subscribe | Unsubscribe | Mail Archives |