Chef vs Fabric: What are the differences?
Chef: Build, destroy and rebuild servers on any public or private cloud. Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others; Fabric: Simple, Pythonic remote execution and deployment. Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks
It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution..
Chef and Fabric can be primarily classified as "Server Configuration and Automation" tools.
"Dynamic and idempotent server configuration" is the top reason why over 104 developers like Chef, while over 19 developers mention "Python" as the leading cause for choosing Fabric.
Chef and Fabric are both open source tools. It seems that Fabric with 11.4K GitHub stars and 1.73K forks on GitHub has more adoption than Chef with 5.85K GitHub stars and 2.36K GitHub forks.
According to the StackShare community, Chef has a broader approval, being mentioned in 360 company stacks & 80 developers stacks; compared to Fabric, which is listed in 147 company stacks and 38 developer stacks.