Docker service discovery using DNS rather than service registry
up vote
0
down vote
favorite
I'm running an application with a multitude of back end services each running within a container. After sifting through various articles, I've reached a state of dilemma as to why do we even employ service registry for service discovery even though our Docker is kind enough to provide us a built in service discovery system?
docker docker-compose containers microservices service-discovery
add a comment |
up vote
0
down vote
favorite
I'm running an application with a multitude of back end services each running within a container. After sifting through various articles, I've reached a state of dilemma as to why do we even employ service registry for service discovery even though our Docker is kind enough to provide us a built in service discovery system?
docker docker-compose containers microservices service-discovery
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm running an application with a multitude of back end services each running within a container. After sifting through various articles, I've reached a state of dilemma as to why do we even employ service registry for service discovery even though our Docker is kind enough to provide us a built in service discovery system?
docker docker-compose containers microservices service-discovery
I'm running an application with a multitude of back end services each running within a container. After sifting through various articles, I've reached a state of dilemma as to why do we even employ service registry for service discovery even though our Docker is kind enough to provide us a built in service discovery system?
docker docker-compose containers microservices service-discovery
docker docker-compose containers microservices service-discovery
asked 2 days ago
Souvik Dey
13225
13225
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Well, I guess it would depend on the scale of your deployment.
Docker is alone sufficient for deployments in a single VM (and docker network) I suppose but what it you want to scale across VMs, Physical Hosts and Datacenters?
Service Discovery would then make more sense and also they give you a totally different level of control compared to relying on the basic implementation that docker provides itself.
So, depending on your deployment it will either be an overkill or a life saver.
Hi Pramodh, I'll be currently using Kubernetes for cluster management and I think Kubernetes has inbuilt DNS server for service discovery. In that regard, does it become necessary to deploy a service registry, as because Kubernetes would already workout all the nitty grity for me. Thanks!
– Souvik Dey
yesterday
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Well, I guess it would depend on the scale of your deployment.
Docker is alone sufficient for deployments in a single VM (and docker network) I suppose but what it you want to scale across VMs, Physical Hosts and Datacenters?
Service Discovery would then make more sense and also they give you a totally different level of control compared to relying on the basic implementation that docker provides itself.
So, depending on your deployment it will either be an overkill or a life saver.
Hi Pramodh, I'll be currently using Kubernetes for cluster management and I think Kubernetes has inbuilt DNS server for service discovery. In that regard, does it become necessary to deploy a service registry, as because Kubernetes would already workout all the nitty grity for me. Thanks!
– Souvik Dey
yesterday
add a comment |
up vote
1
down vote
Well, I guess it would depend on the scale of your deployment.
Docker is alone sufficient for deployments in a single VM (and docker network) I suppose but what it you want to scale across VMs, Physical Hosts and Datacenters?
Service Discovery would then make more sense and also they give you a totally different level of control compared to relying on the basic implementation that docker provides itself.
So, depending on your deployment it will either be an overkill or a life saver.
Hi Pramodh, I'll be currently using Kubernetes for cluster management and I think Kubernetes has inbuilt DNS server for service discovery. In that regard, does it become necessary to deploy a service registry, as because Kubernetes would already workout all the nitty grity for me. Thanks!
– Souvik Dey
yesterday
add a comment |
up vote
1
down vote
up vote
1
down vote
Well, I guess it would depend on the scale of your deployment.
Docker is alone sufficient for deployments in a single VM (and docker network) I suppose but what it you want to scale across VMs, Physical Hosts and Datacenters?
Service Discovery would then make more sense and also they give you a totally different level of control compared to relying on the basic implementation that docker provides itself.
So, depending on your deployment it will either be an overkill or a life saver.
Well, I guess it would depend on the scale of your deployment.
Docker is alone sufficient for deployments in a single VM (and docker network) I suppose but what it you want to scale across VMs, Physical Hosts and Datacenters?
Service Discovery would then make more sense and also they give you a totally different level of control compared to relying on the basic implementation that docker provides itself.
So, depending on your deployment it will either be an overkill or a life saver.
answered yesterday
Pramodh Valavala
38617
38617
Hi Pramodh, I'll be currently using Kubernetes for cluster management and I think Kubernetes has inbuilt DNS server for service discovery. In that regard, does it become necessary to deploy a service registry, as because Kubernetes would already workout all the nitty grity for me. Thanks!
– Souvik Dey
yesterday
add a comment |
Hi Pramodh, I'll be currently using Kubernetes for cluster management and I think Kubernetes has inbuilt DNS server for service discovery. In that regard, does it become necessary to deploy a service registry, as because Kubernetes would already workout all the nitty grity for me. Thanks!
– Souvik Dey
yesterday
Hi Pramodh, I'll be currently using Kubernetes for cluster management and I think Kubernetes has inbuilt DNS server for service discovery. In that regard, does it become necessary to deploy a service registry, as because Kubernetes would already workout all the nitty grity for me. Thanks!
– Souvik Dey
yesterday
Hi Pramodh, I'll be currently using Kubernetes for cluster management and I think Kubernetes has inbuilt DNS server for service discovery. In that regard, does it become necessary to deploy a service registry, as because Kubernetes would already workout all the nitty grity for me. Thanks!
– Souvik Dey
yesterday
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53204242%2fdocker-service-discovery-using-dns-rather-than-service-registry%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password