Abstract
Details coming soon.
Decoupling Local Development from Remote Infrastructure
From the same track
Session
Why Most Platform Teams Fail: The Adoption Problem Nobody Wants to Own
We have all seen the moment: the platform goes live, the launch deck looks sharp, the portal is polished, the golden paths are documented, and yet teams quietly continue doing things the old way. Not always because the platform is bad, but because adoption was assumed, not owned.
Shweta Vohra
Architecture Leader @Booking.com, Author of "Decoding Platform Engineering Patterns" & "Dear Software and AI Architect", 24+ Years Experience Building Cloud, Platform, and AI Systems
Session
Building a Migration Platform: Moving 100+ Netflix RDBMS Workloads to Aurora PostgreSQL
In late 2024, Netflix made a bet: consolidate the vast majority of our relational database use cases onto a single engine: Amazon Aurora PostgreSQL.
Ammar Khaku
Distributed Systems Engineer @Netflix with an Affinity for Online Data Stores
Kshitij Gupta
Software Engineer @Netflix, Building Databases and Distributed Systems
Session
Platform Engineering’s Second Act: From Vending Machine to Passport Control
Three years ago on the QCon SF stage, I made the case for “Acceleration, Autonomy, and Accountability” as the pillars of a successful platform. Those pillars haven't moved. AI has just rewritten what each one requires, and the platform team's job along with it.
Smruti Patel
SVP of Engineering @apollographql
Alex Mann
Senior Engineering Manager @apollographql
Session
The Rise of Agent Enablement: Coding Agents Don't Scale Themselves. Neither Do Your Teams.
In 2009, every big enterprise said "continuous delivery won't work here." In 2026, the same rooms say "the dark factory won't work here." It was never about the technology being ready. It's about the organization being ready. Readiness is a socio-technical problem, not a technical one.
Patrick Debois
AI Product Engineer @Tessl, Co-Author of the "DevOps Handbook", Content Curator at AI Native Developer Community