Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

CDK vs Terraform

This revision card explains CDK vs Terraform. It starts from the need that picking both tools for the same stack without a rule creates double state and pain. It describes CDK — AWS-first, language + constructs, CFN state. Terraform: multi-cloud HCL, its own state, huge provider ecosystem. The how-to section notes choose one IaC tool per stack. Prefer the one your team already reviews in PRs. An example on the card is a greenfield AWS-only TypeScript team often picks CDK; a multi-cloud shop often picks Terraform.

CDK vs Terraform Picking both tools for the same stack without a rule creates double state and pain. CDK: AWS-first, language + constructs, CFN state. Terraform: multi-cloud HCL, its own state, huge provider ecosystem. Choose one IaC tool per stack. Prefer the one your team already reviews in PRs. A greenfield AWS-only TypeScript team often picks CDK; a multi-cloud shop often picks Terraform.
CDK vs Terraform · Download PNG
Read card text

What this card says

Why do we need it?

Picking both tools for the same stack without a rule creates double state and pain.

What is it?

CDK: AWS-first, language + constructs, CFN state. Terraform: multi-cloud HCL, its own state, huge provider ecosystem.

How to do it

Choose one IaC tool per stack. Prefer the one your team already reviews in PRs.

one tool / stack

Example

A greenfield AWS-only TypeScript team often picks CDK; a multi-cloud shop often picks Terraform.

See all AWS revision cards