qqeasonchen
825a1059f1
|
||
|---|---|---|
| docs | ||
| eventmesh-acl | ||
| eventmesh-emesher | ||
| eventmesh-governance | ||
| eventmesh-registry | ||
| eventmesh-sdk-java | ||
| eventmesh-store | ||
| gradle/wrapper | ||
| style | ||
| .coveralls.yml | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| README.md | ||
| build.gradle | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| install.sh | ||
| releasenotes.txt | ||
| settings.gradle | ||
README.md
What is an Event Mesh?
This diagram shows where an event mesh fits in an application stack relative to other technologies such as service mesh:
An event mesh is a configurable and dynamic infrastructure layer for distributing events among decoupled applications, cloud services and devices. It enables event communications to be governed, flexible, reliable and fast. An event mesh is created and enabled through a network of interconnected event meshers.
What are the core capabilities of an event mesh?
This diagram shows the architecture of EventMesh:
An event mesh allows events from one application to be dynamically routed and received by any other application no matter where these applications are deployed (no cloud, private cloud, public cloud). The generic capabilities of an event mesh:
- inherently ‘event-driven;’
- created by connecting event meshers;
- environment agnostic (can be deployed anywhere); and,
- dynamic.
Key components:
- eventmesh-emesher : an middleware to transmit events between event producers and consumers, support cloud native apps and microservices
- eventmesh-sdk-java : support for popular open standard protocols and APIs, including REST/HTTP, AMQP, MQTT, Websocket and JMS, gRPC etc.
- eventmesh-registry : automatically routes events between applications and services connected to seperate event meshers
- eventmesh-governance : governace layer for event producers and consumers
- eventmesh-acl : security at various level of authentication, authorization and topic/channel access control
- eventmesh-store : the store layer of Event-Mesh which implemented with DeFiBus(based on RocketMQ in financial scenario) or RocketMQ by default. We wish the store layeris a general solution and can use any store implement such as kafka, redis ,blockchain etc.
Quick Start
Coming soon...
Contributing
Contributions are always welcomed! Please see CONTRIBUTING for detailed guidelines.
You can start with the issues labeled with good first issue.
License
Apache License, Version 2.0 Copyright (C) Apache Software Foundation