Uploaded October 2024 | Updated September 2026, 2 weeks ago
Matias Pan, a professional maté drinker & Senior Software Engineer at Dagger, is showing us an approach to Infrastructure as Code built with Pulumi.
We look at Go code, discuss procedural (imperative) vs. declarative, spend some time on state management & introduce the concept of Ninjas in the context of infrastructure: move fast & break nothing.
In the second half, Matias uses diagrams to talk through different ideas of rolling this out into production. Which of the two approaches would you choose?
Testing Pulumi programs: pulumi.com/docs/iac/concepts/testing
Listen to the audio version 🎧 https://makeitwork.fm/9
The full content experience 📺 makeitwork.tv
00:00 Why Pulumi instead of Terraform?
02:40 Procedural or declarative?
07:19 What is Ninjastructure?
08:47 First thing that gets provisioned in an AWS account
11:18 How does the network module work?
14:29 Biggest advantage to using Pulumi over Terraform
17:02 Stacks = different environments
18:20 Where is state stored?
20:18 Where did you choose to store the state?
21:46 How to use this in production?
24:32 The GitOps approach
29:17 Outro
Matias Pan, a professional maté drinker & Senior Software Engineer at Dagger, is showing us an approach to Infrastructure as Code built with Pulumi.
We look at Go code, discuss procedural (imperative) vs. declarative, spend some time on state management & introduce the concept of Ninjas in the context of infrastructure: move fast & break nothing.
In the second half, Matias uses diagrams to talk through different ideas of rolling this out into production. Which of the two approaches would you choose?
Testing Pulumi programs: pulumi.com/docs/iac/concepts/testing
Listen to the audio version 🎧 https://makeitwork.fm/9
The full content experience 📺 makeitwork.tv
00:00 Why Pulumi instead of Terraform?
02:40 Procedural or declarative?
07:19 What is Ninjastructure?
08:47 First thing that gets provisioned in an AWS account
11:18 How does the network module work?
14:29 Biggest advantage to using Pulumi over Terraform
17:02 Stacks = different environments
18:20 Where is state stored?
20:18 Where did you choose to store the state?
21:46 How to use this in production?
24:32 The GitOps approach
29:17 Outro
