muteor / microservice_experiment Goto Github PK

Hi I read you interesting blog about this experiment and I found it very interesting...but one thing puzzles me a lot. Having a hard time understanding this example.

For example:

" Use this router for linkerd-to-service
This server should be registered in service discovery so that incoming traffic
is served here."

baseDtab: |
/local => /$/inet/127.1/80;
/http/1.1// => /local ;

My question is:
If this is my linkerd to service router and my application runs on port 80, what' the point of defining port here when you can also use consul to automatically figure that out just like you used it in router for outbound?

It does not makes sense documenting each and every application port in linkerd conf for "linkerd-to-service" router when you can just rely on linkerd-consul namer to do that automatically for you.

Is that makes sense?
Maybe I am not understanding something here correctly....

Hi,

Very interesting exercise, thanks for sharing it! I've arrived here looking for some comparison between Rancher functionalities and Linkerd, Consul, Registrator..., as there seem to be a clear overlap.

You mention that you have added Rancher just for fun. Are you aware of the functional overlap? How would you argue in favor of using Linkerd, Consul, Registrator, instead of Rancher's own internal DNS, metadata service, HA-Proxy based load balancers...?