Terraform vs Yocto: What are the differences?
Developers describe Terraform as "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. On the other hand, Yocto is detailed as "An open Source embedded Linux build system". It is an open source collaboration project that helps developers create custom Linux-based systems regardless of the hardware architecture. It provides a flexible set of tools and a space where embedded developers worldwide can share technologies, software stacks, configurations, and best practices that can be used to create tailored Linux images for embedded and IOT devices, or anywhere a customized Linux OS is needed.
Terraform and Yocto can be categorized as "Infrastructure Build" tools.
Some of the features offered by Terraform are:
- 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.
On the other hand, Yocto provides the following key features:
- Open source embedded Linux build system
- package metadata
- SDK generator
Terraform is an open source tool with 18.2K GitHub stars and 4.92K 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 Yocto is used by Dronesmith Technologies, Koolicar, and Ubidreams. Terraform has a broader approval, being mentioned in 667 company stacks & 1273 developers stacks; compared to Yocto, which is listed in 6 company stacks and 4 developer stacks.
What is Terraform?
What is Yocto?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Yocto?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Terraform?
What are the cons of using Yocto?
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.
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 .
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.