You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sentinel 2.0 will evolve to a universal, cloud-native traffic governance component. Thus we'll need to add fundamental traffic governance building blocks in Sentinel Go 2.0, which at-least cover:
A local "brain" for hinting load balancing
Traffic routing
Traffic tagging as well as carrying tags between services
Outlier eviction
This is the umbrella issue of traffic governance building blocks in Sentinel Go 2.0.
Hello @sczyh30 , may I ask if there is a suitable candidate identified for this issue? I am very interested in this. If you have not selected a candidate yet, I will submit a proposal before the application deadline and may request further communication with you.
Hello, I would like to participate in this issue. I will submit my application on the official platform and sincerely request the opportunity for further communication with you.
Issue Description
Type: feature request
Describe what happened (or what feature you want)
Sentinel 2.0 will evolve to a universal, cloud-native traffic governance component. Thus we'll need to add fundamental traffic governance building blocks in Sentinel Go 2.0, which at-least cover:
This is the umbrella issue of traffic governance building blocks in Sentinel Go 2.0.
Umbrella issue in Java community: alibaba/Sentinel#2943
Sentinel 2.0 将演进为通用、云原生的流量治理组件,并天然支持 OpenSergo 流量治理标准。Sentinel 1.x 的 API 与场景均基于流量策略来进行设计,而未干预流量到来之前的过程,以及中间的执行过程。在 Sentinel 2.0 中,我们需要扩充这一部分的抽象,来支持更多的流量治理能力,其中包括但不限于:
Go 2.0 版本在设计时需考虑 Go 生态对接的便利性,及模型设计。
The text was updated successfully, but these errors were encountered: