Google Git
Sign in
apache / eventmesh / 8c60e3efbefbf274914f842c9308f07a14087766
commit8c60e3efbefbf274914f842c9308f07a14087766[log] [tgz]
authorClay Johnson <cjohnson@gradle.com>Sat Jan 13 23:20:02 2024 -0600
committerGitHub <noreply@github.com>Sun Jan 14 13:20:02 2024 +0800
tree1a961225adf87b3773d150d5bb8e1d15cb0eee41
parent248be85cb3620c4b507b5474fb90eeb02435f10b [diff]
[ISSUE #4737] Separate codeql workflow (#4740)

* Add GRADLE_ENTERPRISE_ACCESS_KEY to a couple of Gradle builds missing it

* Update to most recent Gradle Enterprise Gradle Plugin

* Move CodeQL verification to its own worfklow

* Rename CodeQL workflow to "Analyze"

* Rename "Build" workflow to "Docker"

* Restore the language matrix with 'java' as the only language in ci workflow

* Return the cpp/csharp language step in ci workflow

* Rename CodeQL job to "Analyze" rather than "Build"
4 files changed
tree: 1a961225adf87b3773d150d5bb8e1d15cb0eee41
  1. .github/
  2. .idea/
  3. docker/
  4. eventmesh-common/
  5. eventmesh-connectors/
  6. eventmesh-examples/
  7. eventmesh-filter/
  8. eventmesh-meta/
  9. eventmesh-metrics-plugin/
  10. eventmesh-openconnect/
  11. eventmesh-operator/
  12. eventmesh-protocol-plugin/
  13. eventmesh-retry/
  14. eventmesh-runtime/
  15. eventmesh-sdks/
  16. eventmesh-security-plugin/
  17. eventmesh-spi/
  18. eventmesh-starter/
  19. eventmesh-storage-plugin/
  20. eventmesh-trace-plugin/
  21. eventmesh-transformer/
  22. eventmesh-webhook/
  23. gradle/
  24. resources/
  25. style/
  26. tools/
  27. .asf.yaml
  28. .dockerignore
  29. .gitattributes
  30. .gitignore
  31. .gitmodules
  32. .licenserc.yaml
  33. build.gradle
  34. DISCLAIMER
  35. gradle.properties
  36. gradlew
  37. gradlew.bat
  38. install.sh
  39. LICENSE
  40. maturity.md
  41. NOTICE
  42. README.md
  43. README.zh-CN.md
  44. settings.gradle
README.md




CI status CodeCov Code Quality: Java Total Alerts

License GitHub Release Slack Status

đŸ“Ļ Documentation | 📔 Examples | ⚙ī¸ Roadmap | 🌐 įŽ€äŊ“中文

Apache EventMesh

Apache EventMesh is a new generation serverless event middleware for building distributed event-driven applications.

EventMesh Architecture

EventMesh Architecture

EventMesh Dashboard

EventMesh Dashboard

Features

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:

  • Built around the CloudEvents specification.
  • Rapidty extendsible interconnector layer connectors using openConnect such as the source or sink of Saas, CloudService, and Database etc.
  • Rapidty extendsible storage layer such as Apache RocketMQ, Apache Kafka, Apache Pulsar, RabbitMQ, Redis.
  • Rapidty extendsible meta such as Consul, Nacos, ETCD and Zookeeper.
  • Guaranteed at-least-once delivery.
  • Deliver events between multiple EventMesh deployments.
  • Event schema management by catalog service.
  • Powerful event orchestration by Serverless workflow engine.
  • Powerful event filtering and transformation.
  • Rapid, seamless scalability.
  • Easy Function develop and framework integration.

Roadmap

Please go to the roadmap to get the release history and new features of Apache EventMesh.

Subprojects

Quick start

Here are the guidelines:

Step 1: Deploy eventmesh-store

Step 2: Start eventmesh-runtime

Step 3: Run our demos

Besides, we also provide the docker-version guidelines for you if you prefer Docker:

Step 1: Deploy eventmesh-store using docker

Step 2: Start eventmesh-runtime using docker

Step 3: Run our demos

Contributing

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! :)

CNCF Landscape

Apache EventMesh enriches the CNCF Cloud Native Landscape.

License

Apache EventMesh is licensed under the Apache License, Version 2.0.

Community

WeChat AssistantWeChat Public AccountSlack
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

Mailing List

NameDescriptionSubscribeUnsubscribeArchive
UsersUser discussionSubscribeUnsubscribeMail Archives
DevelopmentDevelopment discussion (Design Documents, Issues, etc.)SubscribeUnsubscribeMail Archives
CommitsCommits to related repositoriesSubscribeUnsubscribeMail Archives
IssuesIssues or PRs comments and reviewsSubscribeUnsubscribeMail Archives