Pure Terraform code is simpler and easier to understand, and if that meets your needs, by all means, stick with it. But as with modern web development, when you scale beyond a certain point, it becomes impractical. It’s like trying to build a complex web app without using frameworks like React-eventually, it’s just not feasible. The same is true with Terraform. If you don’t adopt a framework approach early on, you’ll hit a tipping point: Terraform plans consuming 30GB of RAM, API rate limits being exhausted, and other inefficiencies that become hard to manage and pop up at the worst time. Think of Atmos like a framework, that when followed ensures you can scale infrastructure in a repeatable way, that helps enforce documented best practices for designing cloud architectures. Note this video is 3 years old. Atmos has come a long way since then.

If you already have the skill to manage Arch I highly recommend trying NixOS, it’s the same customization power but all declarative

@@LaloHaohmm, im personally not a Fan of a declarative system but maybe I’ll try it at some time

@@Stefan_-eh2bb As an Arch user playing with nixos in a vm the last couple of days. Really impressed, the best way I can describe it is "medium difficulty". Both things that were a complete pain on arch and things that were ridiculously simple now all take about 1-5 lines in my config to setup regardless of their complexity.

How?