Ansible vs Pulumi: What are the differences?
Ansible: Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine. Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use; Pulumi: Open-source cloud development platform. Pulumi is a cloud development platform that makes creating cloud programs easy and productive. Skip the YAML and just write code. Pulumi is multi-language, multi-cloud and fully extensible in both its engine and ecosystem of packages.
Ansible belongs to "Server Configuration and Automation" category of the tech stack, while Pulumi can be primarily classified under "Infrastructure Build Tools".
Some of the features offered by Ansible are:
- Ansible's natural automation language allows sysadmins, developers, and IT managers to complete automation projects in hours, not weeks.
- Ansible uses SSH by default instead of requiring agents everywhere. Avoid extra open ports, improve security, eliminate "managing the management", and reclaim CPU cycles.
- Ansible automates app deployment, configuration management, workflow orchestration, and even cloud provisioning all from one system.
On the other hand, Pulumi provides the following key features:
- Containers - Deploy a Docker container to production in 5 minutes using your favorite orchestrator.
- Serverless - Stand up a serverless API or event handler in 5 minutes using a real lambda in code.
- Infrastructure - Manage cloud infrastructure or hosted services using infrastructure as code.
Ansible and Pulumi are both open source tools. Ansible with 38.2K GitHub stars and 16K forks on GitHub appears to be more popular than Pulumi with 3.02K GitHub stars and 134 GitHub forks.
What is Ansible?
What is Pulumi?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Pulumi?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
After using Pulumi extensively, it's hard to imagine going back to using Terraform on a regular basis.
Pulumi finally fulfills the promise of writing Infrastructure as code. Not
HCL, but real, honest to goodness code.
The flexibility and power is addictive and empowering. Provision a K8S cluster on EKS, grab the Github webhook source IP's from https://api.github.com/meta, and run Jenkins on the newly provisioned K8S cluster with a helm chart, allowing ingress from Github, all in a few lines of sane, maintainable code.
Ansible is the deployment tool for people who don't like deployment tools. It's close to scripting, doesn't pollute your servers with agents or centralized servers, and just makes immediate sense. The entire stack at Cloudcraft.co is orchestrated by Ansible. What does that mean? Beyond the obvious of installing packages and configuring services, Ansible coordinates all the machines into a working deployment: It adds API servers to the loadbancer pool, opens ports on the DB server for the backend servers to connect, gracefully upgrades services in a rolling fashion for zero-downtime deployments etc. And it's so easy to use, it's easier to use than doing things by hand, meaning it's a deployment tool you'll actually use every time!
We use Ansible to synchronize the few configuration-options we've taken on our CoreOS-Machines. This makes deployment even easier and the fact that it's Agentless made the decision even easier.
Ansible is used in both the development and production deployment process. A playbook couple with a Vagrantfile, easy deploys a local virtual machine that will mirror the setup in production.
I use Ansible to manage the configuration between all of the different pieces of equipment, and because it's agentless I can even manage things like networking devices all from one repo.
- Configuration management:
- deploy/install all web/app environments
- simple with Galaxy and playbooks.
- No need any pre-installed agent on remote servers.