Capistrano vs Docker: What are the differences?
Developers describe Capistrano as "A remote server automation and deployment tool written in Ruby". Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows. On the other hand, Docker is detailed as "Enterprise Container Platform for High-Velocity Innovation". The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere.
Capistrano belongs to "Server Configuration and Automation" category of the tech stack, while Docker can be primarily classified under "Virtual Machine Platforms & Containers".
Some of the features offered by Capistrano are:
- Reliably deploy web application to any number of machines simultaneously, in sequence or as a rolling set
- Automate audits of any number of machines (checking login logs, enumerating uptimes, and/or applying security patches)
- Script arbitrary workflows over SSH
On the other hand, Docker provides the following key features:
- Integrated developer tools
- open, portable images
- shareable, reusable apps
"Automated deployment with several custom recipes" is the primary reason why developers consider Capistrano over the competitors, whereas "Rapid integration and build up" was stated as the key factor in picking Docker.
Capistrano and Docker are both open source tools. It seems that Docker with 54K GitHub stars and 15.6K forks on GitHub has more adoption than Capistrano with 11.1K GitHub stars and 1.71K GitHub forks.
Spotify, Pinterest, and Twitter are some of the popular companies that use Docker, whereas Capistrano is used by Typeform, Bukalapak, and 500px. Docker has a broader approval, being mentioned in 3527 company stacks & 3448 developers stacks; compared to Capistrano, which is listed in 293 company stacks and 81 developer stacks.
lxd/lxc and Docker aren't congruent so this comparison needs a more detailed look; but in short I can say: the lxd-integrated administration of storage including zfs with its snapshot capabilities as well as the system container (multi-process) approach of lxc vs. the limited single-process container approach of Docker is the main reason I chose lxd over Docker.