You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by "qinlonglong123 (via GitHub)" <gi...@apache.org> on 2025/04/29 09:41:06 UTC
[I] [FEATURE] - 是否能够提供一种不需要契约的通信方式 [servicecomb-java-chassis]
qinlonglong123 opened a new issue, #4787:
URL: https://github.com/apache/servicecomb-java-chassis/issues/4787
### Problem this feature would solve
如题。是否能够提供一种不需要契约的通信方式
### Describe the solution
契约虽然让服务消费方式变的简单，但是对于我们的服务可能会面临升级后契约不兼容，而且面临数据丢失重注册性能等问题，契约的维护已经是我们的一个负担。
理论上使用resttemplate的调用方式可以不用契约，因为用户已经组装了rest格式。社区是否考虑使用配置的方式或者提供一种新的接口，让服务间调用不使用契约。
如果社区有意向，我很愿意去分析这个提议的方案。
@liubao68
### Alternatives considered
_No response_
### Additional Context
_No response_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@servicecomb.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [FEATURE] - 是否能够提供一种不需要契约的通信方式 [servicecomb-java-chassis]
Posted by "liubao68 (via GitHub)" <gi...@apache.org>.
liubao68 commented on issue #4787:
URL: https://github.com/apache/servicecomb-java-chassis/issues/4787#issuecomment-2840982627
另外，比较简单的场景，可以参考开发指南： https://servicecomb.apache.org/references/java-chassis/zh_CN/registry/local-registry.html 用本地契约的方式处理，是最优雅的。 这个也适用于第三方调用的场景。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@servicecomb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [FEATURE] - 是否能够提供一种不需要契约的通信方式 [servicecomb-java-chassis]
Posted by "liubao68 (via GitHub)" <gi...@apache.org>.
liubao68 commented on issue #4787:
URL: https://github.com/apache/servicecomb-java-chassis/issues/4787#issuecomment-2840723704
这个问题比较难给出具体的答案。 早期想过是否可以参考feign，可以优先从 interface 直接生成契约， 这个可能是最好的能够兼容现有机制的方案。 不过也可能存在一些特殊问题，特别是edge-service，这意味着edge-service只能使用纯的http转发，类似spring cloud gateway。
当然如果只是寻找一种满足不使用契约的开发模式，可以考虑spring cloud/spring cloud huawei等框架。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@servicecomb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [FEATURE] - 是否能够提供一种不需要契约的通信方式 [servicecomb-java-chassis]
Posted by "liubao68 (via GitHub)" <gi...@apache.org>.
liubao68 commented on issue #4787:
URL: https://github.com/apache/servicecomb-java-chassis/issues/4787#issuecomment-2840979085
上述思路是有代价的。servicecomb将比较长的请求链路: a->b->c 统一了起来，针对微服务调用复杂的场景，处理的非常优雅。 如果不依赖契约， 那么可能会和spring boot/spring mvc一样， 链路只会在a->b的时候比较简化。 在处理a->b->c统一管控的时候，会增加很多额外的复杂性。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@servicecomb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [FEATURE] - 是否能够提供一种不需要契约的通信方式 [servicecomb-java-chassis]
Posted by "liubao68 (via GitHub)" <gi...@apache.org>.
liubao68 commented on issue #4787:
URL: https://github.com/apache/servicecomb-java-chassis/issues/4787#issuecomment-2840727989
上面提到的几种方式应该都能够帮助servicecomb解决一些特定的场景问题，虽然和整体设计思想是偏离的，但从功能上也是很好的补充。 如果您愿意，也是可以接纳这种功能的贡献的。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@servicecomb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [FEATURE] - 是否能够提供一种不需要契约的通信方式 [servicecomb-java-chassis]
Posted by "liubao68 (via GitHub)" <gi...@apache.org>.
liubao68 commented on issue #4787:
URL: https://github.com/apache/servicecomb-java-chassis/issues/4787#issuecomment-2840726847
你说的 “resttemplate的调用方式” 不使用契约是更加困难的，在servicecomb的情形更是如此。 除非是不使用当前servicecomb提供的RestTemplate，而是独立开发一个新的客户端。 这个倒也是一个可行方案，就像edge-service提供了存的http转发机制一样。 但是他们在运行流程和治理规则方面是不一样的，无法很好的融入现有的Filter。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@servicecomb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org