Portainer vs Terraform: What are the differences?
What is Portainer? Simple management UI for Docker. Portainer is an open-source lightweight management UI which allows you to easily manage your Docker environments Portainer is available on Windows, Linux and Mac. It has never been so easy to manage Docker !.
What is Terraform? Describe your complete infrastructure as code and build resources across providers. With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.
Portainer and Terraform are primarily classified as "Container" and "Infrastructure Build" tools respectively.
Some of the features offered by Portainer are:
- Docker management
- Docker UI
- Docker cluster management
On the other hand, Terraform provides the following key features:
- Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.
- Execution Plans: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure.
- Resource Graph: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.
"Simple" is the top reason why over 29 developers like Portainer, while over 81 developers mention "Infrastructure as code" as the leading cause for choosing Terraform.
Terraform is an open source tool with 17.7K GitHub stars and 4.83K GitHub forks. Here's a link to Terraform's open source repository on GitHub.
Uber Technologies, Instacart, and Slack are some of the popular companies that use Terraform, whereas Portainer is used by Viadeo, Betaout, and Bluestem Brands. Terraform has a broader approval, being mentioned in 509 company stacks & 312 developers stacks; compared to Portainer, which is listed in 23 company stacks and 18 developer stacks.
What is Portainer?
What is Terraform?
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 Portainer?
What are the cons of using Terraform?
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
I use Portainer because it does so good with the UI that we don't have to train our whole team to be Linux bash heros. It provides deep details without leaving details behind you would think could only come from the command line. Portainer is a professional tool that gives us enterprise features we appreciate. ( Will be blogging about this in January. )
I use Portainer because we were all in on Docker Cloud, which gave 2 months notice that they were sunsetting their services. We knew we wanted to migrate to Docker Community Edition, but its lack of UI had us worried until we came across Portainer. Portainer had just release their agent feature, which was a critical feature for us. To date, Portainer has been an outstanding product and we couldn't be happier with it.
I use Portainer as a way to disseminate micro-service architectures in my institute and drive innovation forward. Portainer enables an easy to deploy, easy to build platform which decreases the learning curve for deploying containers and micro-services. I am particular interested in offering Portainer as a product in the Research space (i work in one of the bigguest Australian Universities).
I use Portainer because it's a great tool to avoid CLI in docker environment, all management in only one screen, awesome. So we can use our time in more important stuff like providing more and better services to our teams and endusers. The Builtin LDAP support and the internal teams helps a lot in diving Dev's in the Devops world. Long live to Portainer. (I work as DevOps in a Big Brazilian Public University )
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.
We use Terraform because we needed a way to automate the process of building and deploying feature branches. We wanted to hide the complexity such that when a dev creates a PR, it triggers a build and deployment without the dev having to worry about any of the 'plumbing' going on behind the scenes. Terraform allows us to automate the process of provisioning DNS records, Amazon S3 buckets, Amazon EC2 instances and AWS Elastic Load Balancing (ELB)'s. It also makes it easy to tear it all down when finished. We also like that it supports multiple clouds, which is why we chose to use it over AWS CloudFormation.
I use Terraform because it hits the level of abstraction pocket of being high-level and flexible, and is agnostic to cloud platforms. Creating complex infrastructure components for a solution with a UI console is tedious to repeat. Using low-level APIs are usually specific to cloud platforms, and you still have to build your own tooling for deploying, state management, and destroying infrastructure.
However, Terraform is usually slower to implement new services compared to cloud-specific APIs. It's worth the trade-off though, especially if you're multi-cloud. I heard someone say, "We want to preference a cloud, not lock in to one." Terraform builds on that claim.
Terraform Google Cloud Deployment Manager AWS CloudFormation
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 .
Hey Team, As I used portainer and here I think some of functionality must be there like visualiser for monitoring.
And Here I found a issue when we open the console then does not allow to exit the terminal using exit commands and scroller is not work in terminal...
On the road to greatness. A worthy challenger soon to be
Terraform makes it so easy to deploy AWS and Google Cloud services, with the declarative approach avoiding so many headaches of manual work and possible mistakes.
- Infrastructure as Code.
- Central tool to deploy all infratructure: AWS, CloudFlare, StatusCake
The entire AWS environments is described and setup using Terraform.