Infrastructure-as-Code with Pulumi- Better than all the others (like Ansible)?
There's a new Infrastructure-as-Code (IaC) kid on the block: Pulumi is there to frighten the established: Chef, Puppet, Terraform, Cloudformation, Ansible... But is it really the "better" tool and how could they be compared? Is it only hype-driven? We'll find out, incl. lot's of example code. (ContainerConf / Continuous Lifecycle 2019 Talk in Mannheim)
Example GitHub code: https://github.com/jonashackt/pulumi-python-aws-ansible
There‘s this 3rd comparison called Procedural vs.
But remember the
4. Tools shouldn‘t suck
(no master!, no agents!)
master no master
• central place to see status of your
• continuously enforce configuration
in the background
• extra infrastructure!
• needs to be maintained
• client-2-master & master-2-servers
communication needs ports & security
Crosswalk for AWS supports “day
one” tasks, such as creating your
initial container-based workloads
using ECS/Fargate/EKS & serverless
workloads (API Gateway / Lambda)
No matter what IaC tool you use…
Automatically update dependencies
Use Testframeworks – or even do TDD!
Run Tests automatically - in your
Continuous Integration Pipeline!
Treat your infrastructure code
Always aim for reproducible builds (aka
Run your infrastructure code frequently!
(scheduled CI jobs)