Packer vs Pulumi: What are the differences?
Packer: Create identical machine images for multiple platforms from a single source configuration. Packer automates the creation of any type of machine image. It embraces modern configuration management by encouraging you to use automated scripts to install and configure the software within your Packer-made images; 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.
Packer and Pulumi can be categorized as "Infrastructure Build" tools.
Some of the features offered by Packer are:
- Super fast infrastructure deployment. Packer images allow you to launch completely provisioned and configured machines in seconds, rather than several minutes or hours.
- Multi-provider portability. Because Packer creates identical images for multiple platforms, you can run production in AWS, staging/QA in a private cloud like OpenStack, and development in desktop virtualization solutions such as VMware or VirtualBox.
- Improved stability. Packer installs and configures all the software for a machine at the time the image is built. If there are bugs in these scripts, they'll be caught early, rather than several minutes after a machine is launched.
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.
Packer and Pulumi are both open source tools. Packer with 9.09K GitHub stars and 2.48K forks on GitHub appears to be more popular than Pulumi with 3.02K GitHub stars and 134 GitHub forks.
What is Packer?
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 Packer?
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
LaunchDarkly is almost a five year old company, and our methodology for deploying was state of the art... for 2014. We recently undertook a project to modernize the way we #deploy our software, moving from Ansible-based deploy scripts that executed on our local machines, to using Spinnaker (along with Terraform and Packer) as the basis of our deployment system. We've been using Armory's enterprise Spinnaker offering to make this project a reality.
Our base infrastructure is composed of Debian based servers running in Amazon EC2 , asset storage with Amazon S3 , and Amazon RDS for Aurora and Redis under Amazon ElastiCache for data storage.
We are starting to work in automated provisioning and management with Terraform , Packer , and Ansible .
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.