For the last decade, we treated infrastructure as a separate discipline. You wrote your Node.js app, and then you wrote hundreds of lines of HCL (Terraform) to define VPCs, Subnets, Security Groups, and IAM roles just to deploy it. A newer class of tools is trying to remove that duplication, and for some workloads it already works well.
IfC (Infrastructure from Code)
The concept is simple: many infrastructure requirements are already implicit in your application code.
If you import a `Queue` object and call `queue.push()`, the platform should automatically provision an SQS queue or a Redis instance. You shouldn't have to declare it twice.
resource "aws_sqs_queue" "q" {
name = "orders"
visibility_timeout = 60
}
resource "aws_iam_role" "..." {...}
// ... 200 more lines
import { Queue } from 'your-ifc-framework';
const orders = new Queue('orders');
// hypothetical: the tool infers a queue + IAM from this
await orders.push(payload);
The "Compiler" for Cloud
Infrastructure-from-code frameworks work like compilers for the cloud: they parse your AST (Abstract Syntax Tree). They see that you are accessing a `bucket`, so they create the S3 bucket. They see you are running a scheduled task, so they create the scheduler rule. The trade-off is control: you accept the framework's defaults and its supported cloud services in exchange for writing less configuration.
Less Drift
When the code *is* the infrastructure definition, it becomes much harder for your infrastructure to drift from your application logic, because both change in the same commit.
Terraform is not going away. For multi-cloud estates, strict compliance and shared platform modules, explicit infrastructure code is still the safer choice. For a new service with standard building blocks, letting tooling infer the plumbing can save real effort. If you want a second opinion on which fits your setup, our DevOps and cloud team works with Terraform, Docker and Kubernetes on AWS, GCP and Cloudflare, or you can talk to us about your platform.
