From 71f69f7419af7b2d2e6ab1b3f32bd5285f56e25e Mon Sep 17 00:00:00 2001 From: Armon Dadgar Date: Thu, 10 Apr 2014 14:50:58 -0700 Subject: [PATCH] website: remove fabric comparison --- website/source/intro/vs/fabric.html.markdown | 27 -------------------- 1 file changed, 27 deletions(-) delete mode 100644 website/source/intro/vs/fabric.html.markdown diff --git a/website/source/intro/vs/fabric.html.markdown b/website/source/intro/vs/fabric.html.markdown deleted file mode 100644 index 9972681825..0000000000 --- a/website/source/intro/vs/fabric.html.markdown +++ /dev/null @@ -1,27 +0,0 @@ ---- -layout: "intro" -page_title: "Serf vs. Fabric" -sidebar_current: "vs-other-fabric" ---- - -# Serf vs. Fabric - -Fabric is a widely used tool for system administration over SSH. Broadly, -it is used to SSH into a group of nodes and execute commands. Both Fabric -and Serf can be used for service management in different ways. - -While Fabric -sends commands from a single box, Serf instead rapidly broadcasts a message -to the entire cluster in a distributed fashion. Fabric has a number of advantages -in that it can collect the output of commands and stop execution if an -error is encountered. Serf is unable to do these things since it has no single -destination to send logs to, nor does it have any control flow. However, -Fabric must be provided with a list of nodes to contact, whereas membership -is built directly into Serf. Additionally, Serf is able to propagate a message -within seconds to an entire cluster, allowing for much higher parallelism and -scalability. - -Fabric is much more capable than Serf at system administration, but it is -limited by its execution speed and lack of node discovery. Combined together, -Fabric can query Serf for nodes and make use of message broadcasts where -appropriate, using direct SSH exection when and where output is needed.