luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

website: some vs copy changes

This commit is contained in:
Mitchell Hashimoto 2014-04-14 11:58:40 -07:00
parent 2c207b4044
commit 938d15e630
3 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.gitignore vendored
View File

@ -2,6 +2,7 @@
*.o
*.a
*.so
Thumbs.db
# Folders
_obj

2
website/source/intro/vs/chef-puppet.html.markdown
View File

@ -32,7 +32,7 @@ without a slow convergence run. Lastly, because each datacenter runs indepedentl
supporting multiple datacenters is no different than a single datacenter.
That said, Consul is not a replacement for configuration management tools.
These tools are still critical to setup setup applications and even to
These tools are still critical to setup applications and even to
configure Consul itself. Static provisioning is best managed
by existing tools, while dynamic state and discovery is better managed by
Consul. The separation of configuration management and cluster management

8
website/source/intro/vs/skydns.html.markdown
View File

@ -20,7 +20,8 @@ However, the systems differ in many ways. Consul provides a much richer
health checking framework, with support for arbitrary checks and
a highly scalable failure detection scheme. SkyDNS relies on naive
heartbeating and TTLs, which have known scalability issues. Additionally,
the heartbeat only provides a limited liveness check.
the heartbeat only provides a limited liveness check, versus the rich
health checks that Consul is capable of.
Multiple datacenters can be supported by using "regions" in SkyDNS,
however the data is managed and queried from a single cluster. If servers
@ -35,5 +36,6 @@ scopes the managed data to be per-datacenter. This means each datacenter
runs an independent cluster of servers. Requests are forwarded to remote
datacenters if necessary. This means requests for services within a datacenter
never go over the WAN, and connectivity issues between datacenters do not
affect availability within a datacenter.
affect availability within a datacenter. Additionally, the unavailability
of one datacenter does not affect the service discovery of services
in any other datacenter.