I believe dubbo-proxy will become an important component of Dubbo in the near future, it’s a good start to mobilize people thinking on what we want to define dubbo-proxy.
Seems like we get lots of works to do😀 I think it would be better if we can share the meeting schedule in advance to this mailing list several days before it’s being held so more people interested can join. Jun > On Aug 9, 2020, at 11:46 PM, Cheng Tie <[email protected]> wrote: > > Dear all, > > dubbogoproxy第一次会议纪要 > 2020-08-07与会人员 > > - 于雨 > - 何鑫铭 > - 邹毅贤 > - 潘天颖 > - 冯振宇 > - 铁城 > - 鞠东 > - 张其 > - 郭洋 > - 郑先乐 > - 王翔 > - 张俊杰 > > 会议纪要 > > 我们通过钉钉会议进行了dubbogo-proxy 的第一次会议，沟通了对 dubbogo-proxy 的理解以及对将来的一些想法。现在汇总讨论内容如下： > 定位 > > 类似于数据面板。 > 起源 > > 1. 目前服务网格对 dubbo 的支持并不友好； > 2. 通过 dubbogo-proxy 的发展能够反向推进 dubbogo 发展； > 3. 目前没有社区统一的 dubbo 网关； > 4. 有利于 dubbo 整个生态发展，并有一定市场需求； > > 特性 > > 对整个功能的初步设想 > > 1. 协议转换：优先 HTTP 转 Dubbo 和 HTTP 反向代理，协议可扩展； > 2. 服务能力：服务调用，动态服务发现； > 3. 路由配置：静态、动态路由； > 4. 参数装饰：通过扩展机制对请求、响应内容修改； > 5. 流量管理：负载均衡、限流、熔断、灰度； > 6. 安全：认证、授权，IP黑白名单，TLS； > 7. 扩展性：Filter机制，插件机制，可插拔，易开发； > 8. 稳定性：热更新（执行配置，插件）； > 9. 部署：集群方案，sidecar 方案； > 10. 可观测性：完善的日志，监控、告警，统计 如：QPS指标； > > > ------ English ------ > Summary > > We conducted the first meeting of dubbogo-proxy through the DingTalk > meeting to communicate our understanding of dubbogo-proxy and some > ideas for the future. The summary of the discussion is as follows: > Definition > > Similar to the data panel. > Origin > > 1. Service mesh is not very friendly to dubbo; > 2. The development of dubbogo-proxy can promote the reverse > development of dubbogo; > 3. There is no community unified dubbo gateway at present; > 4. It is conducive to the overall ecological development of dubbo, > and has certain market demand; > > Features > > A preliminary conception of the whole function: > > 1. Common protocol conversion: priority http to dubbo and http > reverse proxy, protocol scalability; > 2. Service capability: service invocation, dynamic service discovery; > 3. Routing configuration: static and dynamic routing; > 4. Parameter decoration: The content of request and response is > modified by extension mechanism. > 5. Visit policy: load balancing, limiting rate, degrade, dark launch; > 6. Security: authentication, authorization, IP black and white list, TLS; > 7. Extensibility: filter chan plug-in supported, dynamic pluggable, > easy to develop; > 8. Stability: hot deployment (execution configuration, plug-in); > 9. Deployment: cluster scheme, sidecar scheme; > 10. Observability: open tracing, log, monitoring, alarm, > statistics, such as: QPS indicators;
