We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I wonder if this is the right setup for consul connectable service.
Host/VM 1 : Consul server Host/VM 2 : Consul Agent (client mode) , registrator and connectable and All micro-services
So when I started my micro-services containers, I could see them in consul server.
Question : If I have two micro-services.... how do I load balance them ?
What API (rest API) should I call to get the services in a round robin fashion ?
How does connetable helps ?
Since connectable is sitting on each host ...does it do roundrobin of micro-services distributed across the hosts ?
Praveen
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I wonder if this is the right setup for consul connectable service.
Host/VM 1 : Consul server
Host/VM 2 : Consul Agent (client mode) , registrator and connectable and All micro-services
So when I started my micro-services containers, I could see them in consul server.
Question :
If I have two micro-services.... how do I load balance them ?
What API (rest API) should I call to get the services in a round robin fashion ?
How does connetable helps ?
Since connectable is sitting on each host ...does it do roundrobin of micro-services distributed across the hosts ?
Praveen
The text was updated successfully, but these errors were encountered: