BlogWissenwertesTerraform: Conclusion

Terraform: Conclusion

Ein Beitrag von Thomas Mohrbacher

Why Terraform? – Part IV

After our previous blog posts in part I, part II, and part III, where we delved into the world of Terraform, providing a brief introduction, exploring its core principles, and taking a closer look at the pros and cons as well as alternative solutions, we are now reaching the conclusion of this Terraform series, offering a brief summary.


Today, there are numerous options for managing infrastructure as code, and selecting one framework does not necessarily mean excluding others automatically. The choice of which framework to use can often come down to personal preference, especially when it involves decisions regarding the programming language to be used.

In our current project situation, Terraform provides the best support for hybrid cloud systems on one hand, and a basic, well-structured planning framework on the other.

While the native tools of AWS, Azure or Googles may offer better integration with their respective cloud systems, they may lack support for different ones.

Pulumi is also a strong candidate, with its flexibility and Terraform provider support. However, by using CDKTF, we can enable the use of multiple languages if desired, while retaining HCL as the default for colleagues who are not familiar with languages such as Java, C#, Python, etc


With the drawbacks of Terraform in mind, some of these issues can be mitigated by adopting best practices and delving deeper into the HCL language and the framework’s implementation.

In line with this, in our upcoming series, we aim to share insights on how to organize Terraform projects, link different projects or sources together, and leverage the full potential of complex variables.

And now…

We hope we were able to give you insightful insights into this world with our Terraform series.
In the future, we will take a closer look at other interesting topics from the IT world and share them with you here on the blog. Keep you updated!!

Schreiben Sie einen Kommentar

Ihre E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert