Meetup - The Present and The Future of Infrastructure as Code
Tell Me More!
The goal is to discuss Infrastructure as Code with several experts and lightning talks by the community (no boring sales pitches).
This HUG meetup will be in English and will talk about the Present and The Future of Infrastructure as Code:
- Pulumi, Terraform, CDK, other ?
- What do you think about Components and Higher-level constructs?
- Why is the DX experience an afterthought?
- Is type safety overrated?
- How many IaC tools does it take to change a light bulb?
- Ask your question beforehand here
Join us if you are curious about DevOps, Infrastructure as Code, Terraform, Pulumi, CDKs, and everything in between!
Agenda
â° Meetup on Tuesday 11th of October from 6 PM.
đ đ„€ 18:00 - Snacks and non-alcoholic drinks (sponsored by Couchbase). Time to mingle.
âĄïž 19:00 - Lightning talk - 10 minutes max, by the community, no sales pitches, straight to the point. Call for speakers is open!
đ€ 19:30 - Round table (in English) - the Present and The Future of Infrastructure as Code - with industry experts:
âïž Paul Stack works as an engineering manager at Pulumi Corporation and is an expert in DevOps, IaC, and many other areas.
âïž Matthieu Napoli is an AWS Hero, former PM of Serverless Framework, and author of Lift, integrating AWS CDK with Serverless Framework.
âïž Sebastian Korfmann is an AWS Hero and the original creator of Terraform for CDK.
âïž Anton Babenko (moderator) is an AWS Hero, Terraform influencer, and open-source maintainer of AWS Terraform modules.
Want to Join Us?
You need to be in Paris on the 11th of October and register by following this link!
.svg)
.svg)
.svg)
Suggested articles
In the 2026 regulatory landscape, manual audits are a liability. This guide explores using GitOps to generate DORA-compliant audit trails through IaC, drift detection, and automated segregation of duties. Discover how the Qovery management layer turns compliance into an architectural output, reducing manual overhead for CTOs and Senior Engineers.
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
A multi-cluster Kubernetes architecture distributes application workloads across geographically separated clusters rather than a single environment. This strategy strictly isolates failure domains, ensures regional data compliance, and guarantees global high availability, but demands centralized Day-2 control to prevent exponential cloud costs and operational sprawl.
Stop overpaying for Kubernetes observability. Learn how in-cluster monitoring and AI-driven troubleshooting with Qovery Observe can eliminate APM ingestion fees, reduce SRE bottlenecks, and make your cloud costs predictable.
.webp)