Abstract

Load testing tells you what happened. Observability tells you why. But too often these disciplines operate independently, leaving teams manually piecing together performance regressions with server-side telemetry after the fact. This talk introduces the key concepts behind correlating load testing metrics with infrastructure and application observability data, and why automating that correlation is a force multiplier for reliability and informed decision-making.

Bio

Heather Thacker is a Developer Advocate at Gatling where she enjoys building content and community around making performance testing approachable and essential to teams. Her perspective is shaped by five years as a software developer followed by three years advocating for DevOps best practices. She’s an international speaker that enjoys comparing theory with reality of software development lifecycles, using practical examples and analogies. Her goal is to give engineers different perspectives that will build the confidence they need to make performance a core part of their workflow.

Daniel Coll Leal began his tech journey at a startup 10 years ago as a mobile developer. Over the years, he worked at several consulting companies, gaining some experience across multiple stacks. Eventually, he specialized in web development and observability and is now focused on advocating for the field by creating technical content, conducting workshops and giving talks.

Abstract

The exponential growth of Generative AI (GenAI) is simultaneously revolutionizing business and creating an unsustainable demand on global energy infrastructure. Are you ready to scale your Cloud capabilities without compromising your corporate sustainability goals? Our presentation introduces a strategic framework for Sustainable Cloud Solutions that turns resource intensity into an opportunity for operational efficiency and environmental stewardship. Stop settling for legacy infrastructure that strains the grid and join the movement toward performant systems engineered for a zero-carbon future. This presentation tackles the urgent and growing environmental footprint of GenAI, driven by its high-resource training and deployment. We will detail the alarming reality of GenAI training clusters, which exhibit an intense power density consuming 7-8 times the energy of typical workloads, rapidly necessitating reliance on fossil fuel-based data centers. Using concrete examples, such as the estimated 1,287 MWh and 552 tons of CO2 generated by the training of a major model like GPT-3, we establish the critical need for change. We then pivot to the practical application of Performance Engineering and Sustainable Software Development—the only viable solution to manage these demands. The session will cover key mitigation strategies ranging from architectural redesigns to code-level optimizations. Attendees will leave this session equipped with actionable knowledge and a strategic roadmap to immediately reduce the environmental and operational cost of their Cloud Solutions. You will learn how to: Implement Green Coding Practices: Discover specific techniques to optimize code for maximum computational efficiency and minimum energy consumption. Architect for Sustainability: Master the adoption of Sustainable Software Architectures, including the strategic deployment of serverless computing and microservices to ensure resources are consumed only during active execution, eliminating wasteful energy use from idle servers. Apply Energy-Efficient Algorithms: Identify and deploy algorithms and data structures that offer equivalent performance with a significantly smaller energy and carbon footprint, future-proofing your GenAI projects.

Bio

Almudena is of a mathematical vocation and has been dedicated to performance engineering for 18 years. Almudena has worked on projects with high traffic and high availability from online television platforms, job portals, security proxies, and now a European retailer. For 15 years, she has been actively involved in the dissemination of DevOps and performance culture in Spain. She is also an activist for the integration of female talent in STEM in Spain.

Abstract

Cloud platforms make it incredibly easy to deploy infrastructure in minutes, but they also make it surprisingly easy to create costly mistakes that quietly inflate cloud bills and reduce system reliability. In this talk, I will explore some of the most common and expensive mistakes teams make when running cloud infrastructure at scale. Drawing from real-world SRE experience operating cloud-native systems, this session highlights practical examples of how these issues appear in production environments and how teams can identify and avoid them. Attendees will leave with a better understanding of the hidden pitfalls in cloud infrastructure and practical strategies to build systems that are not only reliable, but also cost-efficient.

Bio

Focuses on improving reliability, observability, and cost efficiency in cloud-native environments. I'm passionate about sharing practical lessons from operating real systems and regularly contributes to the DevOps and SRE community through talks and knowledge sharing.

Abstract

In this session, we'll explore the architecture best practices and AWS tooling that enable organizations to design highly available and disaster-resilient workloads in the cloud. We'll start by laying the foundation with High Availability patterns, and then we will talk about AWS Toling like Well Architected Framework, Route 53 Application Recovery Controller, AWS Elastic Disaster Recovery and Fault Injection Service (FIS)

Bio

Oriol Matavacas is a Sr. Solutions Architect at AWS based in Barcelona, primarily supporting customers on their journey to the Cloud. He enjoys building new solutions with scalability, availability, and ease of maintenance by leveraging serverless architectures.

Abstract

At STACKIT we run a multi-tenant Git platform with hundreds of tenants. Customer data is off-limits. By design, not by accident. We have no access to their repositories, no way to inspect their traffic, no debugging backdoor. So how do you know customers are having a good experience when you can’t look at what they’re doing? Our answer is canary tenants. A synthetic tenant that we provision in production alongside the real ones, running end-to-end checks every minute. Control plane journeys, data plane journeys, all on infrastructure we own. Zero risk to customer data. In this talk I’ll walk through the architecture with CanaryChecker, how we keep synthetic traffic out of our real-user SLIs, and why running canaries in production gives better signal than an isolated staging environment. I’ll also cover what canary tenants can’t tell you. Tenant-specific config drift. Data-at-scale issues. Every feature outside the happy path. These are blind spots we’ve chosen to accept rather than close, and I’ll explain why.

Bio

Diego is a Senior SRE at STACKIT Cloud. He spends his days operating multi-tenant developer tooling and his nights wondering whether the alerts that didn’t fire meant everything was fine or that his monitoring is lying to him.

Abstract

One very common assumption of Kubernetes practicioners, even those in the network side of things, is that Kubernetes Services behave like good old load balancers. And to a certain extent, Services do behave in a similar fashion to what one would typically classify as a round-robin load balancer. However, the reality of it is much deeper than that. Both simpler and more complex at the same time. In this talk we'll go over an incident we had on September 2025, where a mix of this misconception, Istio's behavior, CoreDNS' failure, kube-proxy's silence, and iptables and conntrack interoperability made it look like everything was OK, yet DNS—it's always DNS—was failing. We will go deep into how brilliantly simple Kubernetes' networking is, how Istio's DNS works on top of Kubernetes' DNS, and how both broke each other.

Bio

Ricard is a Lead Site Reliability Engineer at Cisco ThousandEyes' SRE team. You can often find him investigating the weirdest incidents, such as the one that motivated this talk. Ricard is currently writing a book about homelabbing, so go talk to him if you have a homelab!

Abstract

How do you plan for unplanned incidents? You practice with Chaos Engineering. Strong incident response doesn’t just happen, you have to build the skills and train your team. Practicing for major incidents gives your team insight into how your applications will behave when something goes wrong as well as how the team will interact to solve problems. Combining your Incident Response practices with Chaos Engineering roots your response practice in real-world scenarios, helping your team build confidence.

Bio

Daniel Afonso is a Senior Developer Advocate at PagerDuty, SolidJS DX team member, Instructor at Egghead.io, and Author of State Management with React Query. Daniel has a full-stack background, having worked with different languages and frameworks on various projects from IoT to Fraud Detection. He is passionate about learning and teaching and has spoken at multiple conferences around the world about topics he loves. In his free time, when he's not learning new technologies or writing about them, he's probably reading comics or watching superhero movies and shows.

Abstract

Remember when you knew all your servers by name and deployed changes with a single SSH command? Now imagine doing that when your link comes in 10-minute windows every few hours, and bandwidth is a precious commodity measured in kbps. Welcome to DevOps in Space. At Sateliot, our Infrastructure & Software Engineering team works at the intersection of aerospace, telecommunications and software. We build modern distributed systems and then send them to an environment where normal expectations -low latency, immediate feedback, up-to-date systems- simply don’t apply. In this talk I’ll give a high-level tour of the challenges that make space and telco different: intermittent and low-bandwidth connectivity, long feedback loops, constrained devices, and the cultural gaps between aerospace, telco and software teams. I'll also share some adaptations that allow us to apply some of the DevOps processes and tools that have become industry standards.

Bio

I started as a sysadmin when workloads ran on bare metal and Devs were the enemies of Ops. The industry changed and we changed with it, but at the end of the day we're still the ones that receive an alert when things stop working.

Abstract

Your Internal Developer Platform lives in two worlds. In the Right Side Up, developers rely on self‑service observability and resiliency to build, deploy, operate and debug their apps. In the Upside Down, the platform itself must be observable to ensure its reliability, performance, resiliency and to understand usage patterns and adoption. The twist? these two worlds are not separate. Improving observability and resiliency of the platform directly improves the observability and resiliency for the applications built on top of it. Just like in Stranger Things, observability and resiliency becomes the bridge that connects both realities In this talk you learn real-world OpenTelemetry-based best practices to observe the core layers of your platform such as your Git, Argo, Backstage and k8s! You learn how to derive SLOs from that data to increase resiliency for your platform and the apps and services deployed through your platform!

Bio

Andreas Grabner (@grabnerandi) has 25+ years of experience as a software developer, tester and architect and is an advocate for high-performing cloud scale applications. He is a CNCF ambassador, contributor to the CNCF project keptn, Co-Author of Platform Engineering for Architects and a Fellow DevRel for Dynatrace. Andreas is also a regular contributor to the DevOps, Platform Engineering and Cloud Native community and a frequent speaker at technology conferences. In his spare time you can most likely find him on one of the salsa dancefloors of the world!

Abstract

The next evolution of incident response isn’t faster alerts, it’s autonomous resolution. Join ilert CEO Birol Yildiz as he shows how AI SRE agents now diagnose and remediate outages without waking anyone up. Learn how these systems combine observability data, deployment context, and code intelligence to restore services in minutes and hand over clean incident reports instead of 3 a.m. pages.

Bio

Birol Yildiz is the Co-founder and CEO of ilert, adeptly steering the company with a rare combination of technical and product expertise. His prior experience includes a significant role as Chief Product Owner for Big Data products at REWE Digital. With a strong foundation in computer science, Birol bridges the gap between developer and product strategist, constantly striving to innovate and provide customer-centric solutions at ilert.