| commit | c7fdf35af5f0655a7a4eca5b3ba38698d060290d | [log] [tgz] |
|---|---|---|
| author | nanoxiong <Xiong_mengfei@163.com> | Thu Aug 20 17:23:11 2020 +0800 |
| committer | GitHub <noreply@github.com> | Thu Aug 20 17:23:11 2020 +0800 |
| tree | 06971ae31b37cd009413b99b490c4a42eb210a9c | |
| parent | 6a02afa2a4ff0674febbabb0d2f3a1728a471e36 [diff] | |
| parent | 4c9c6de81ec0c87ad152e7502e7a5cb63288b5c2 [diff] |
Merge pull request #138 from WeBankFinTech/develop merge develop into master , pre release 1.0.0
This figure shows the positioning of the event mesh relative to other similar technologies (such as service mesh) in the application framework.
Landscape of EventMesh:
Event Mesh is a dynamic plug-in cloud-native basic service layer used to decouple the application and middleware layer. It provides flexible, reliable and fast event distribution, and can be managed. This diagram shows the architecture of EventMesh:
The event mesh allows events from one application to be dynamically routed to any other application. General functions of the event mesh:
Dependent components:
Key components:
Contributions are always welcomed! Please see CONTRIBUTING for detailed guidelines
You can start with the issues labeled with good first issue. GitHub Issues
Apache License, Version 2.0 Copyright (C) Apache Software Foundation
WeChat group: