Smartstacl vs. consul - Introduction
-
Upload
marcin-skarbek -
Category
Software
-
view
75 -
download
5
Transcript of Smartstacl vs. consul - Introduction
SmartStack vs. ConsulIntroduction
Docker Meetup Kraków29.04.2015
Marcin Skarbek@marcinskarbek
Capabilities
SmartStack• service discovery• health checking
Consul• service discovery• health checking• key/value store
Components
SmartStack• Synapse• Nerve
• ZooKeeper• HAProxy
Instead of ZooKeeper• Serf• Etcd
Consul• Consul
Installation
SmartStack• Nerve on each server
• Synapse and HAProxy on each client• ZooKeeper as a backend
Consul• Consul on each node• 3/5 as a servers (Raft)
• rest as a clients
How does it work
SmartStack
• Nerve checks serverand register it into the backend
• Synapse pulls info about serversand register them in HAProxy
• client connects to server through HAProxy
Consul
• Consul checks server and registers it• client connects to server
using DNS record or Web API
Pros
SmartStack
• no igerention into application• fairly easy deployment
Consul
• single binary file• very easy deployment
Cons
SmartStack
• Ruby• statically configured ZooKeeper
• HAProxy health checks can be expensive• lots of small load balancers
Consul
• using API requires integration• Raft low performance
Thanks!
photo: leolintang CC BY 2.0https://www.flickr.com/photos/28581681@N04/4256458866