Skip to main content

SkyDNS vs Consul

Competition is a good thing and that someone at HasiCorp decided to compare SkyDNS to Consul is also a good thing. I'm just a little tweaked about the biased nature of the review even though I cannot find fault with wanting to come out on top.

Getting SkyDNS started is as simple as:
  1. start etcd if not already running (systemctl start etcd2)
  2. pull SkyDNS from the docker registry (docker pull skynetservices/skydns)
  3. set your SkyDNS config (etcdctl set /skydns/config '{"dns_addr":"","ttl":3600, "domain":"nuc.local", "nameservers": ["",""]}')
    1. you must restart SkyDNS after any config change
    2. only supports one domain
    3. passthru to other nameservers
  4. launch SkyDNS (docker run -it --net host --name skydns skynetservices/skydns)
  5. install a test record (etcdctl set /skydns/local/nuc/bob '{"host":"","port":8080}')
  6. test SkyDNS (dig @localhost bob.nuc.local)
  7. remove the test record (etcdctl rm /skydns/local/nuc/bob)
Some of the criticism from the mentioned reviewer was the distributed datacenter. SkyDNS does not really support that model even though the reviewer said it did and that under DR conditions it was slow to recover. Frankly these statements are WRONG. SkyDNS relies on etcd which does not specifically have a spanning datacenter feature. Partitioned datacenters are common and WAN distributed systems with highlevel of dependency an replication are a problem unto themselves.

In more concise terms. The reviewer said that Consul handled partitioned networks better but then fails to recognize that if the datacenters were partitioned that the dependent distributed services might also be partitioned.
The one benefit of Consul over SkyDNS is a false example.
Operations teams know that there are a number of costs associaed cross datacenter transactions and network reliability, latency, throughout and costs... Consul offers no distinct advantage here. etcd, on the other hand, separates the storage from the protocol.

Lastly; the reviewer makes the point that both HTTP and DNS protocols are supported. In a way that is true, however, to be precise the HTTP(s) service is actually provided by etcd and not SkyDNS.

PS: as of this point in time version 3 of etcd is newly available although I do not know what new and improved features to expect.


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

Agile is still dead and has been since 1991

[updated 2011.09.30] yet another response to Agile is good.
When you have so much of you career invested in something like Agile, XP etc... it can be hard to see the forest for the trees. I had a consulting job in The Haag many years ago. IBM was the incumbent contractor at the customer site (a bank) but after 5 years on the job they had not written a single line of functioning code. In the office there were two teams of software people... both behind closed doors. The first team was the Data team and the second team was Functional. They rarely spoke and they never shared information. I was there for a week, introduced the client to OO and we had a functioning prototype. Smart people do smart things, You cannot make an underachiever exceptional by using Agile. Either they get "it" or they don't.
I just commented on a blog. I'm sure there is some validity to his post beyond observing that Agile Scrum is broken. It certainly is not what it was originally intended but for…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…