Hi community, I'd like to propose a discussion about integration with the OpenSergo service governance spec, which was initiated by open-source communities from companies including Alibaba, bilibili and ByteDance.
OpenSergo is a set of general-purpose, language-agnostic cloud-native service governance specifications, which are based on scenarios and best practices of microservice governance. The most significant highlight of OpenSergo is that it defines service governance rules with a unified set of configuration/DSL/protocol, oriented to multi-language, heterogeneous architecture. Whether the language of the microservice is Java, Go, Node.js or other languages, from gateway to microservice, from database to cache, from service discovery to service config, developers can leverage the unified OpenSergo CRD to perform unified governance for each component in microservice architecture. We hope to build further connections with the Apache APISIX community, where we can discuss and refine the general service governance specification together, including traffic routing, rate limiting, fault tolerance and more. With the integration with OpenSergo spec, developers could leverage the unified OpenSergo spec CRD to achieve the unified governance in both gateway layer and microservice layer, which may bring more connections with other communities for APISIX, enabling the nouveau worth of APISIX-based microservice architecture. OpenSergo 是一套开放、通用的、面向分布式服务架构、覆盖全链路异构化生态的服务治理标准，基于业界服务治理场景与实践形成服务治理通用标准。OpenSergo 的最大特点就是以统一的一套配置/DSL/协议定义服务治理规则，面向多语言异构化架构，做到全链路生态覆盖。无论微服务的语言是 Java, Go, Node.js 还是其它语言，无论是标准微服务还是 Mesh 接入，从网关到微服务，从数据库到缓存，从服务注册发现到配置，开发者都可以通过同一套 OpenSergo CRD 标准配置针对每一层进行统一的治理管控，而无需关注各框架、语言的差异点，降低异构化、全链路服务治理管控的复杂度。 我们希望可以联合 Apache APSIX 社区进行进一步的合作，社区来一起讨论与定义一套统一的服务治理标准。我们的 Apache APSIX 可以适配实现该标准，通过同一套 OpenSergo CRD 标准配置针对流量网关层进行统一的治理管控，可以释放基于 Apache APSIX 的微服务架构的新价值。 以下是近期发布的 OpenSergo v1alpha1 中流量路由、流控降级与容错相关标准，我们找到了一些和 Apache APISIX 比较好的结合点，也欢迎社区一起讨论： 流量路由：将具有某些属性特征的流量，路由到指定的目标。流量路由是流量治理中重要的一环，我们可以基于流量路由标准来实现各种场景，如灰度发布、金丝雀发布、容灾路由、标签路由等。 流控降级与容错：同样是服务流量治理中关键的一环，以流量为切入点，通过流控、熔断降级、流量平滑、自适应过载保护等手段来保障服务的稳定性。 我们在社区发起了一个issue，欢迎大家通过issue或者邮件列表参与讨论，一起制定与建设这一块的标准：https://github.com/apache/apisix/issues/7381 Best Regards, OpenSergo Community
