📦 Documentation | 📔 Examples | ⚙️ Roadmap | 🌐 简体中文
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.
EventMesh supports multiple Event Stores, the default storage mode is
standalone, and does not rely on other event stores as layers.
Download the latest version of the Binary Distribution from the EventMesh Download page and extract it:
wget https://dlcdn.apache.org/eventmesh/1.10.0/apache-eventmesh-1.10.0-bin.tar.gz tar -xvzf apache-eventmesh-1.10.0-bin.tar.gz cd apache-eventmesh-1.10.0
start.sh script to start the EventMesh Runtime server.
View the output log:
tail -n 50 -f logs/eventmesh.out
When the log output shows server
state:RUNNING, it means EventMesh Runtime has started successfully.
You can stop the run with the following command:
When the script prints
shutdown server ok!, it means EventMesh Runtime has stopped.
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
Enter the container:
sudo docker exec -it eventmesh /bin/bash
view the log:
cd logs tail -n 50 -f eventmesh.out
Run the following commands(To delete a deployment, simply replace
$ cd eventmesh-operator && make deploy
kubectl get pods 、
kubectl get crd | grep eventmesh-operator.eventmeshto see the status of the deployed eventmesh-operator.
$ kubectl get pods NAME READY STATUS RESTARTS AGE eventmesh-operator-59c59f4f7b-nmmlm 1/1 Running 0 20s $ kubectl get crd | grep eventmesh-operator.eventmesh connectors.eventmesh-operator.eventmesh 2024-01-10T02:40:27Z runtimes.eventmesh-operator.eventmesh 2024-01-10T02:40:27Z
Execute the following command to deploy runtime, connector-rocketmq (To delete, simply replace
$ make create
kubectl get pods to see if the deployment was successful.
NAME READY STATUS RESTARTS AGE connector-rocketmq-0 1/1 Running 0 9s eventmesh-operator-59c59f4f7b-nmmlm 1/1 Running 0 3m12s eventmesh-runtime-0-a-0 1/1 Running 0 15s
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.
Here is the List of Contributors, thank you all! :)
Apache EventMesh enriches the CNCF Cloud Native Landscape.
Apache EventMesh is licensed under the Apache License, Version 2.0.
|WeChat Public Account
|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
|Development discussion (Design Documents, Issues, etc.)
|Commits to related repositories
|Issues or PRs comments and reviews