And while that’s technically true, it’s not helpful. What makes this even harder is that most of the comparisons you find online between these tools do little more than list the general properties of each tool and make it sound like you could be equally successful with any of them. All of them are well documented, both in terms of official documentation and community resources such as blog posts and StackOverflow questions. All of them are open source, backed by large communities of contributors, and work with many different cloud providers (with the notable exception of CloudFormation, which is closed source and AWS-only). All of these tools can be used to manage infrastructure as code. What’s not easy is figuring out which one of these you should use. If you search the Internet for “infrastructure-as-code”, it’s pretty easy to come up with a list of the most popular tools: In this post, we’re going to discuss why we picked Terraform as our IAC tool of choice. In the intro to the series, we discussed why every company should be using infrastructure-as-code (IAC). This is Part 1 of the Comprehensive Guide to Terraform series. Update, Sep 28, 2022: We’ve updated this blog post series for Terraform 1.2 and released the 3rd edition of Terraform: Up & Running ! Update, J: We’ve updated this blog post series for Terraform 0.12 and released the 2nd edition of Terraform: Up & Running ! Update, Novem: We took this blog post series, expanded it, and turned it into a book called Terraform: Up & Running !
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |