[Discussion] About Adding Traffic Governance to the Event Message Model | 关于增加事件消息模型的流量治理

[JasonChen86899]

Refer to the EDA event driven model to manage the flow of event messages. At present, there are the following governance aspects

1. Event production governance, including synchronous and asynchronous traffic control and exception handling

2. Event consumption management, including traffic control and exception handling

3. Event pipeline governance. Pipeline refers to the governance of various types of mq or memory queues. It refers to the standardized control of pipelines, such as the management of topics

4. Event flow audit refers to the audit of the traffic at the entrance and exit of the data at each stage

---

参考EDA事件驱动模型，对事件消息进行流量治理。目前有如下治理方面

1. 事件生产治理，包括同步异步的流量管控和异常兜底处理
2. 事件消费治理，包括流量管控和异常处理
3. 事件管道治理，管道指各类型mq或者内存队列 这方面的治理指的是对管道进行规范化的管控如对topic进行管理
4. 事件审计，指数据在各个阶段的出入口流量的审计

[JasonChen86899]

@sczyh30 hi eric 可否看下这个议题或者也可以在双周会上讨论

[sczyh30]

@sczyh30 hi eric 可否看下这个议题或者也可以在双周会上讨论

Of course :) 欢迎下个社区周会来分享与讨论，社区周会的参与 可以钉钉联系我哈：sczyh30

[JasonChen86899]

当前进展:

• 初步确定事件治理PB 协议
• 跟 EM 社区人员对齐协议并有如下修改: 1. 具体化事件目标对象 2. 审计策略单独列出 以及 修改事件主题下的策略配置 3. 根据pb定义列出一个示例

[sczyh30]

最新设计文档：https://alidocs.dingtalk.com/i/nodes/OBldywvrKxo89j1Nkw4bWQk2ngpNbLz4?corpId=dingeb32b4fe069868b1f5bf40eda33b7ba0&utm_medium=im_card&iframeQuery=utm_medium%3Dim_card%26utm_source%3Dim&utm_source=im