dubbo3(http1\http2\tri\grpc)+higress  #13639

Activity

1. zhangyungen

   added

   type/discussionEverything related with code discussion or questionEverything related with code discussion or question

   on Jan 12, 2024
2. chickenlj commented on Jan 16, 2024

   

   chickenlj

   on Jan 16, 2024

   Last edited by chickenlj

   Contributor

   More actions

   Please check the features and best practices we are working on with the upcoming dubbo 3.3 release.

   https://dubbo-next.staged.apache.org/zh-cn/overview/mannual/java-sdk/tasks/gateway/triple/

   Please notice that contents in the above link are all in experimental or developing phase.
3. zhangyungen commented on Jan 17, 2024

   

   zhangyungen

   on Jan 17, 2024

   Last edited by zhangyungen

   Author

   More actions

   Please check the features and best practices we are working on with the upcoming dubbo 3.3 release.

   https://dubbo-next.staged.apache.org/zh-cn/overview/mannual/java-sdk/tasks/gateway/triple/

   Please notice that contents in the above link are all in experimental or developing phase.

   明白谢谢，3.3 release 将实现triple 的网关代理，但是没有实现dubbo-provider之间调用的网关代理。

   我的意思是，多个dubbo-provider之间的rpc流量也可通过微服务网关代理，这样所有服务间流量都经过微服务网关，微服务网关上就可以做很多服务治理与流量质量相关事项，类似sidecar模式，但是比sidecar轻量。如此这样dubbo-consumer 发起请求不是直接流向provider。而是变成 consumer ----> gateway----->provider 。

   如此，流量治理监控，服务治理，服务熔断、限流、降级，甚至业务监控，完全可以收拢在网关编排，或者增加扩展处理，在跨语言，跨框架的service+mesh中，减去了多套实现，多套管理。

   👍React with 👍1Reacted by mytang0
4. AlbumenJ

   added this to Dubbo Boardon Mar 7, 2024
5. apache

   locked and limited conversation to collaborators on Mar 11, 2024
6. AlbumenJ

   converted this issue into a discussion #13886 on Mar 11, 2024
7. github-project-automation

   moved this to Done in Dubbo Boardon Mar 11, 2024