Operations | Monitoring | ITSM | DevOps | Cloud

Behind every modern.NET application is an ADO.NET provider handling database connections, queries, and ORM operations behind the scenes. As applications become more cloud-native and data-intensive, that provider layer has become far more important than many teams realize. Performance, scalability, deployment reliability, and even developer workflow can all depend on the quality of the provider underneath the application.

Many of us understand the concept of Kubernetes Requests and Limits, and that by reducing over-sized resource requests we can reduce waste in our clusters. And for GKE Autopilot and EKS Fargate clusters that is true. Because you’re being billed directly for the resources you’re requesting, driving down requests can result in instantaneous savings. However in most hosted Kubernetes environments you’re not actually being billed for requests.

The low-code promise failed for 15 years. AI builders delivered in 15 months. Here's what actually changed, why the engineer in me resisted it, and what it means for every CTO. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

AI tools turned everyone into a builder. Your sales team, your finance team, your CEO - they're all shipping apps now. The answer isn't to ban them. It's to give them a governed platform they actually want to use. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

Picture this. You’re standing up a new service. Cursor or Claude Code wrote most of the controller, and it calls a payment API your team doesn’t own. Now you need tests. The agent is gamely inventing the response shape from whatever OpenAPI doc you fed it (which is a year stale), and the WireMock stubs it just generated are guesses dressed up as JSON. Three weeks later production breaks, the test suite was green the whole time, and nobody knows where to start looking.

Open source thrives on engineering-driven processes. Fast feedback loops, terminal tools, Git workflows: they’re the lifeblood of how we build software in the open. But for software to truly excel, we need to create user experiences that empower people to use them. I wanted to bring this conversation into the spotlight as part of Canonical’s Open Design initiatives. What better way than at FOSS Backstage 2026 Berlin?