This figure shows the positioning of the event grid relative to other similar technologies (such as service grid) in the application framework
Event grid is a dynamic plug-in basic service layer used to distribute events among decoupled applications, cloud services and devices. It enables the communication of events to be supervised and governed, and the communication of events is flexible, reliable and fast.
This diagram shows the architecture of EventMesh:
The event grid allows events from one application to be dynamically routed to any other application. General functions of the event grid:
- Essentially "event driven";
- Event can be governanced;
- Dynamic routing;
- Cloud native
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.
- Build and deploy eventmesh-store, see instruction 'eventmesh-store quickstart'
- Build adn deploy eventmesh-emesher, see instruction 'eventmesh-emesher quickstart'.
- Run eventmesh-sdk-java demo, see instruction 'eventmesh-sdk-java quickstart'.
Contributions are always welcomed! Please see CONTRIBUTING for detailed guidelines.
You can start with the issues labeled with good first issue.
Apache License, Version 2.0 Copyright (C) Apache Software Foundation
WeChat group：
