Hey everyone :wave: I’ve been exploring IaC tools ...
# random
a
Hey everyone 👋 I’ve been exploring IaC tools recently, especially how Pulumi compares with Terraform and OpenTofu in real-world use. i have put together some thoughts here: https://dev.to/muskan_8abedcc7e12/infrastructure-as-code-best-practices-terraform-pulumi-and-opentofu-in-2026-4nc1 i would love any feedback from you all, also would love to know how you people are using pulumi in production or alongside other tools.
n
Good read, well structured, valid points, touches the major downsides\caveats of terraform at scale. 👏 Nitpick - Missing info on strategies to reduce state size using outputs from other workspaces: from my experience splitting terraform monolithic workspaces by using workspace outputs is extremely fragile and awkward as opposed to the easy simple and convenient interface of Pulumi stack references. not a fair comparison: but in a 2800 resources TF monolithic, I only managed to chain 2 workspaces together before stuff was too hard to debug or broke with Pulumi I got multiple parallel chains of 1-2 stacks deep (app->middleware->core) references
a
Thanks, really appreciate this! 🙌 That’s a great point, i didn’t go deep into workspace splitting and cross-workspace dependencies. Interesting to hear how quickly it becomes hard to manage at scale. The Pulumi stack references example is really helpful. I’ll explore that more.
f
I really enjoyed reading this @adamant-furniture-24101 (I work at Pulumi) - thank you for your thoughts! I especially liked the stat about how 2/3rds of IaC teams have meaningful drift and most don't even know about it until something blows up on the next apply. I can totally believe this! If you want to explore any other ideas with one of our Solutions Architects let me know and I'd be happy to arrange a no obligation chat with them.
a
@full-analyst-99298 Appreciate it, Dipali! And yeah, drift is such a massive headache in reality. I would love to chat more. Sending you a DM!