State locking with DynamoDB in Terraform - Time & Space Complexity

Time Complexity: State locking with DynamoDB

O(n)

Understanding Time Complexity

When Terraform uses DynamoDB for state locking, it prevents multiple users from changing infrastructure at the same time.

We want to understand how the number of locking operations grows as more users or actions happen.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

terraform {
  backend "s3" {
    bucket         = "my-terraform-state"
    key            = "state.tfstate"
    region         = "us-west-2"
    dynamodb_table = "terraform-lock"
    encrypt        = true
  }
}

resource "aws_dynamodb_table" "terraform_lock" {
  name         = "terraform-lock"
  billing_mode = "PAY_PER_REQUEST"
  hash_key     = "LockID"
  attribute {
    name = "LockID"
    type = "S"
  }
}

This config sets up DynamoDB to lock the Terraform state during changes, ensuring only one operation happens at a time.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: DynamoDB API calls to acquire and release locks on the state.
• How many times: Once per Terraform operation that modifies state (e.g., plan, apply).

How Execution Grows With Input

Each Terraform action tries to lock the state once, regardless of how many resources are managed.

Input Size (n)	Approx. Api Calls/Operations
10	10 lock/unlock calls
100	100 lock/unlock calls
1000	1000 lock/unlock calls

Pattern observation: The number of locking operations grows linearly with the number of Terraform actions, not the number of resources.

Final Time Complexity

Time Complexity: O(n)

This means the locking operations increase directly with the number of Terraform actions performed.

Common Mistake

[X] Wrong: "Locking time grows with the number of resources managed in Terraform."

[OK] Correct: Locking happens once per operation, not per resource, so resource count does not increase locking calls.

Interview Connect

Understanding how state locking scales helps you design reliable infrastructure workflows and avoid conflicts in team environments.

Self-Check

"What if multiple Terraform operations run in parallel? How would the time complexity of locking change?"