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
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
AI is helping developers write more code, faster than ever. But writing code is only half the story. What happens after? Building, deploying, debugging, scaling. That's where teams still lose hours.We're building Qovery for this era. Not just to deploy your code, but to make everything that comes after writing it just as fast.
By adopting GitOps and utilizing management platforms like Qovery, fintech teams can automatically generate DORA-compliant audit trails, transforming regulatory compliance from a manual, time-consuming chore into an automated, native byproduct of their infrastructure.
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.
.webp)