We've been using CDK for Terraform[1] for a year or two for both AWS and GCP. It's working great. We especially like that it supports Typescript.<p>[1] <a href="https://developer.hashicorp.com/terraform/cdktf" rel="nofollow">https://developer.hashicorp.com/terraform/cdktf</a>
<a href="https://opentofu.org/" rel="nofollow">https://opentofu.org/</a> is better than terraform, as it’s a fork that happened before terraform became not open source.
Terraform and the CDK use different programming models to achieve similar goals. The CDK takes a more dynamic scripting approach much like Gradle, while Terraform is more descriptive and declarative. Functionally, I think they have similar capabilities.
If you plan on making your devs do all your infra work, maybe CDK would be better. But you will eventually regret not having TF and its huge ecosystem of modules and integrations.
It might not matter _that much_ depending on the complexity of the application you're modeling.<p>There are lots of options. A few things to consider:<p>- Is it a dedicated individual or group responsible for the IaC? What are they comfortable with?
- Details about the running app will need to find their way into the infra somehow (env vars at least), if it's a separate group or individual, what will be the most obvious process to perform that exchange of information?<p>I wrote a short piece about point two [1]. Disclosure: I work at a company building a platform with its own opinionated IaC.<p>1. <a href="https://noop.dev/blog/build-apps-not-infrastructure/" rel="nofollow">https://noop.dev/blog/build-apps-not-infrastructure/</a>