You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by GitBox <gi...@apache.org> on 2021/09/10 03:59:38 UTC

[GitHub] [servicecomb-java-chassis] diwenzheng opened a new issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

diwenzheng opened a new issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563


   首先集成三方url配置的yaml或者自己使用bean来注册,官方文档只是说明针对三方的接口实现服务治理的过程,过于服务治理这块能详细告诉我下做了哪些,怎么做的吗,想学习下经验.


-- 
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



[GitHub] [servicecomb-java-chassis] diwenzheng commented on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
diwenzheng commented on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-917363521


   @liubao68  这块的问题 麻烦帮我解答下.我要考虑我们自己的三方服务应用有没有必要改造这块.


-- 
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



[GitHub] [servicecomb-java-chassis] diwenzheng commented on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
diwenzheng commented on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-916687363


   > java-chassis提供的第三方调用不是把第三方信息注册到注册中心。 而是在本地构造一个虚拟的微服务,包括其服务信息和实例信息。 这样就可以像请求其他注册到注册中心的java-chassis服务一样访问了。
   
   一般情况下第三方只会提供一个虚拟ip又或者负载均衡的vip,那么他如何针对这块做服务治理,还有比如我的实例如20个,每一个都需要在本地构建一个虚拟微服务,那么当20个实例中的其中一个发现Ip不通,这时候会熔断吗又或者访问过多会限流吗?当其中一个实例发现问题,所有实例共享这个信息,还是自己管自己呢?


-- 
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



[GitHub] [servicecomb-java-chassis] diwenzheng edited a comment on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
diwenzheng edited a comment on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-917403897


   其实我主要关心的是,上面我们说的其实是在本地构造一个虚拟微服务,多实例的时候,其中一个实例限流或者熔断,其余实例是自动感知到随后熔断还是每个是独立的.想得到的答案是多实例时,关于本地构造虚拟微服务是如何管理的.


-- 
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



[GitHub] [servicecomb-java-chassis] liubao68 commented on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
liubao68 commented on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-917372184


   > java-chassis提供的第三方调用不是把第三方信息注册到注册中心。 而是在本地构造一个虚拟的微服务,包括其服务信息和实例信息。 这样就可以像请求其他注册到注册中心的java-chassis服务一样访问了。
   
   前面这里实际已经回答这个问题了。 如果java-chassis之间的客户端调用相关的功能能满足要求, 那么就能满足要求。 
   
   [案例](https://blog.csdn.net/looook/article/details/116271333) 里面包含了一些优秀实践,可以参考


-- 
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



[GitHub] [servicecomb-java-chassis] diwenzheng commented on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
diwenzheng commented on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-917403897


   其实我主要关心的是,上面我们说的其实是在本地构造一个虚拟微服务,多实例的时候,其实一个实例限流或者熔断,其余实例是自动感知到随后熔断还是每个是独立的.


-- 
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



[GitHub] [servicecomb-java-chassis] diwenzheng edited a comment on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
diwenzheng edited a comment on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-917403897


   其实我主要关心的是,上面我们说的其实是在本地构造一个虚拟微服务,多实例的时候,其实一个实例限流或者熔断,其余实例是自动感知到随后熔断还是每个是独立的.想得到的答案是多实例时,关于本地构造虚拟微服务是如何管理的.


-- 
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



[GitHub] [servicecomb-java-chassis] liubao68 commented on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
liubao68 commented on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-917803443


   如果是实例隔离, 那么错误统计是基于实例的。 如果是“服务接口”隔离”(参考bizkeeper模块基于hystrix的实现,或者基于流量的治理部分), 那么隔离是针对所有实例的。 
   
   也就是效果取决于实际采用的治理策略。 


-- 
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



[GitHub] [servicecomb-java-chassis] diwenzheng edited a comment on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
diwenzheng edited a comment on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-917403897


   其实我主要关心的是,上面我们说的其实是在本地构造一个虚拟微服务,多实例的时候,其中一个实例限流或者熔断,其余实例是自动感知到随后大家迅速熔断或限流.还是每个都是是独立的,自己管理自己.想得到的答案是多实例时,关于本地构造虚拟微服务是如何管理的.


-- 
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



[GitHub] [servicecomb-java-chassis] diwenzheng closed issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
diwenzheng closed issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563


   


-- 
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



[GitHub] [servicecomb-java-chassis] liubao68 commented on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
liubao68 commented on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-916681104


   java-chassis提供的第三方调用不是把第三方信息注册到注册中心。 而是在本地构造一个虚拟的微服务,包括其服务信息和实例信息。 这样就可以像请求其他注册到注册中心的java-chassis服务一样访问了。 


-- 
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



[GitHub] [servicecomb-java-chassis] diwenzheng commented on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
diwenzheng commented on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-916610879


   @liubao68 


-- 
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



[GitHub] [servicecomb-java-chassis] diwenzheng edited a comment on issue #2563: 2.5.0 关于将第三方url注册到自己的注册中心这块的疑问

Posted by GitBox <gi...@apache.org>.
diwenzheng edited a comment on issue #2563:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2563#issuecomment-916687363


   > java-chassis提供的第三方调用不是把第三方信息注册到注册中心。 而是在本地构造一个虚拟的微服务,包括其服务信息和实例信息。 这样就可以像请求其他注册到注册中心的java-chassis服务一样访问了。
   
   一般情况下第三方只会提供一个虚拟ip又或者负载均衡的vip,那么他如何针对这块做服务治理,还有比如我的实例如20个,每一个都需要在本地构建一个虚拟微服务,那么当20个实例中的其中一个发现Ip不通,这时候会熔断吗又或者访问过多会限流吗?当其中一个实例发现问题,所有实例共享这个信息,还是自己管自己呢?
   
   那么如果能熔断或者限流该如何配置呢?


-- 
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