Bosses, cloud novice, consult the ribbon and feign in cloud architecture inside the location of the what kind of? Watch a lot of are still a little fuzzy, feign inherits the ribbon, why still need to use ribbon? Thank you, look on a post said: there is a remote call, Ribbon will from Eureka registry pull down data selected a machine to Feign to initiate a remote call, if so, whether can be understood as a Ribbon to Feign calls to the specified server (in order to achieve the purpose of load balancing)? How to don't have to Feign to directly load balancing? Deliver!

CodePudding user response:

His top!!!!!!

CodePudding user response:

Hear because spring Cloud project within the scope of each module has its own business, will be more clear, what modules do what, what modules do not...

CodePudding user response:

2 floor right, high cohesion and low coupling, that is not his own things don't do it

CodePudding user response:

Directly use Nginx, anyway, it's no use Ribbon

CodePudding user response:

Since you mentioned the position, I can only say that in the new, ribbon and feign have been cloud out

CodePudding user response:

Simple understanding to Feign packaging on the Ribbon with a layer of,
Ribbon can be directly used alone, not in SpringCloud service means can be used and then the Ribbon + "service address management" to complete the Ribbon of load balancing, below is a sample used alone: https://blog.csdn.net/songzehao/article/details/101315206

And is often used directly in SpringCloud Feign, make "Service address management" can be done through Eureka and other components to cooperate, at the same time also makes the across Service invocation easier, like call another interface in the same Service or another Service, so Feign more automated and easy, of course, its core is still a Ribbon,