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?










share|improve this question


























    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?










    share|improve this question
























      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?










      share|improve this question













      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 2 days ago









      Souvik Dey

      13225




      13225
























          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.






          share|improve this answer





















          • 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











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          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
































          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.






          share|improve this answer





















          • 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















          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.






          share|improve this answer





















          • 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













          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.






          share|improve this answer












          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.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          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


















          • 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


















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          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




















































































          Popular posts from this blog

          How to pass form data using jquery Ajax to insert data in database?

          National Museum of Racing and Hall of Fame

          Guess what letter conforming each word