Speakers
Bijlmerdreef 106
1102 CT Amsterdam, Netherlands
How do you abstract platform complexity without sacrificing control, visibility, or flexibility across multi-cloud environments? As modern architectures push toward microservices, Kubernetes, and GitOps, the gap between development and operations continues to widen. Enter Radius, not your typical mathematical calculations around circles, but a CNCF sandbox project. It offers a universal, open-source framework that standardizes application development and deployment while decoupling workloads from infrastructure. This session explores how Radius enables platform teams to define reusable, compliant patterns and gives developers self-service workflows, without losing governance. With native GitOps integration and support for cloud and on-prem, Radius delivers consistency, collaboration, and operational clarity. Learn how to build scalable, future-ready platforms that balance autonomy and control through a shared, declarative abstraction layer.
Yash is a software engineer and researcher with a deep interest in distributed systems. His focus is on observability and performance, areas where he constantly seeks new insights. As an active advocate of OpenTelemetry, Yash contributes to both the project and the wider community. Outside of tech, he’s an avid explorer, whether in the kitchen experimenting with new recipes or traveling the world to taste diverse cuisines.
Kubernetes is dynamic—and so are its threats. Traditional security tools struggle to keep up. In this session, we’ll explore how eBPF powers next-gen observability and security by running directly in the Linux kernel. Using Cilium for networking and Tetragon for runtime security, we’ll trace system calls, enforce behavior-based policies, and detect threats in real time—all without sidecars or agents. By the end, you’ll understand how to turn the kernel into your security ally.
Hello, I'm Mert Polat.
I'm currently working as an Cloud and Platform Engineer at Sufle. I started my career as a Jr. DevOps Engineer at Zip Turkey, where I gained extensive experience in Infrastructure and DevOps domains. At Duzce MEKATEK, I worked in the software team for an autonomous vehicle project and took on a leadership role. Additionally, I honed my skills in technologies like Docker, Kubernetes, and Ansible during a DevOps internship at Formica.
I am passionate about technology and knowledge sharing, so I write various articles for @DevopsTurkiye and @Bulut Bilişimciler publications on Medium.
I graduated from Duzce University with a degree in Computer Programming, and I'm currently pursuing a bachelor's degree in Management Information Systems at Anadolu University.
Batuhan, a.k.a. developer-guy, is well-known in the Turkish cloud native community. He’s been highly active in the Software Supply Chain Security space and has contributed to several CNCF projects such as Flux, Kyverno, and ko. He’s also one of the key organizers behind DevOpsTr, CNCF Istanbul Chapter, and KCD Turkey. Notably, he won the “Best Sigstore Evangelist” award and was part of the program committee for the first-ever SigstoreCon. He’s passionate about open source, has written 10+ technical blog posts published on official project websites, and continues to grow the community through meetups, workshops, and online initiatives.
Services are the backbone of our systems. They are the pieces that make up our businesses—whether they are literal microservices or functional components of a traditional application, we can’t do the computer thing without services.
When it comes to a service in your company or organization, who’s responsible for it? The cast of characters involved in the lifecycle of a service is more than just software engineers. It can include program managers, product owners, sustainability teams (SREs/operations engineers), and business stakeholders, just to name a few.
Topics covered in this talk include: – Defining what a service means to you and your organization – Roles in service ownership – What are you observing about your service? – How you want a team to respond to a service outage or incident – Managing your service in production – Tuning your service – Understanding how the service impacts the business
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.
Lambda provides multi-AZ support out of the box, but even then, things can still go wrong in production.
Region-wide outages and performance degradations can render your applications non-responsive. And what if you're dealing with downstream systems that aren't as scalable as your system and can't handle the load you put on them?
The bottom line is that many things can go wrong, and they often do at the worst of times. The goal of building resilient systems is not to prevent failures, but to design systems that can withstand them.
In this talk, we will examine several practices and architectural patterns that can help you build more resilient serverless architectures, such as multi-region design, employing DLQs and surge queues and cell-based architectures.
We'll also explore how chaos experiments can help us identify failure modes before they happen in production.
Yan is an experienced engineer who has run production workload at scale on AWS since 2010. He has been an architect and principal engineer in a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. He has worked extensively with AWS Lambda in production since 2015. Nowadays, he splits his time between advancing the state of serverless observability as a Developer Advocate at lumigo.io and helping companies around the world adopt serverless as an independent consultant.
Yan is also an AWS Serverless Hero and a regular speaker at user groups and conferences internationally. He is the author of Production-Ready Serverless and co-author of Serverless Architectures on AWS, 2nd Edition. And he keeps an active blog at theburningmonk.com and hosts a serverless-focused podcast at realworldserverless.com.
The Model Context Protocol (MCP) has seen a meteoric rise to become the de-facto connecting mycelium for GenAI models and applications. In this session, we will explore the critical role of API management in securing MCP servers. Learn how to leverage API management as the "USB-c" connector for your Copilot, ensuring seamless and secure integration. We will cover best practices, real-world examples, and practical tips to enhance your server security and streamline operations. Join us to discover how API management can be the key to unlocking robust security for your MCP servers.
Alessandro, a seasoned community leader, has spent the last few years architecting cloud-native infrastructures for Microsoft customers, energizing the Dutch tech community, and helping professionals achieve CKx certification. With over 25 years immersed in open-source technologies, Alessandro is deeply passionate about the cloud-native ecosystem. He's now back at Microsoft as a Senior Technical Specialist in Application Innovation & AI.
In the world of DevOps and SRE, we pride ourselves on automation, observability, and engineering excellence. But even the most sophisticated infrastructure can be derailed by something far more human: our own brains.
This talk explores the invisible enemies of reliability — cognitive biases that affect how engineers make decisions, solve problems, and respond to incidents. From confirmation bias during outages to groupthink in postmortems, we’ll unpack six specific mental shortcuts that silently undermine your systems.
Each bias is brought to life with real-world engineering examples, memorable visuals, and practical strategies you can apply immediately. You’ll hear relatable war stories — like how anchoring on a bad hypothesis prolonged a major incident, or how optimism bias led to a Friday deployment that ended in disaster.
More than a lecture, this is a wake-up call. We don’t need more YAML linters or dashboards. We need to debug ourselves.
By the end of the session, attendees will: • Understand how specific biases impact reliability and team performance • Recognize symptoms of biased thinking in real-world DevOps workflows • Learn actionable techniques to create more resilient, self-aware engineering cultures
This talk is ideal for DevOps engineers, SREs, team leads, and reliability advocates looking to take their incident management and system design to the next level — not by adding more tools, but by thinking more clearly.
As the founder of Melomar-IT, I am dedicated to demystifying complex IT concepts and providing clear, actionable insights to professionals and enthusiasts alike. With a robust background in Platform Engineering, DevOps, and Site Reliability Engineering (SRE), I specialize in creating content that bridges the gap between intricate technical subjects and practical understanding. Professional Expertise: • Platform Engineering: Designing and managing scalable, efficient, and secure IT infrastructures that support seamless application development and deployment. • DevOps Engineering: Implementing and promoting DevOps best practices to enhance collaboration, automate workflows, and accelerate software delivery. • Site Reliability Engineering (SRE): Ensuring system reliability, performance, and scalability through proactive monitoring, automation, and incident response strategies. • IT Education and Content Creation: Developing comprehensive IT explainers and tutorials that empower individuals to enhance their technical skills and stay abreast of industry trends. Melomar-IT on YouTube: Through Melomar-IT, I produce and share content focused on: • In-Depth Tutorials: Step-by-step guides on Platform Engineering, DevOps tools, and SRE practices. • Industry Insights: Analysis of current trends and emerging technologies in the IT sector. • Practical IT Explainers: Simplifying complex concepts for better understanding and application. Mission: My goal is to equip IT professionals and enthusiasts with the knowledge and tools necessary to excel in the rapidly evolving tech landscape. By fostering a community centered on continuous learning and growth, I aim to inspire innovation and excellence in the field of Information Technology. Connect with Me: I am always eager to connect with fellow professionals, share insights, and explore collaborative opportunities. Feel free to reach out to discuss all things IT, from Platform Engineering and DevOps to the latest industry developments.
Using multiple Availability Zones (AZs) is often seen as essential for building resilient and highly available cloud systems. This is true, until it is not. While Multi-AZ is a proven architectural choice, there are important drawbacks to consider and common assumptions that don’t always hold up. There are also different ways to implement it, each with its own trade-offs.
In this session, we will explore the Multi-AZ journey, separating fact from fiction. We will discuss when Multi-AZ truly helps, the costs involved, and some surprising side effects that are often overlooked.
Renato has extensive experience as a cloud architect, tech lead, and cloud services specialist. He lives in Berlin and works remotely as a principal cloud architect. His primary areas of interest include cloud services and relational databases. He is an editor at InfoQ and a recognized AWS Data Hero.
Over One year of operating Karpenter in production across multiple Kubernetes Clusters has taught us at adjoe many valuable lessons that we want to share in this talk. We will talk about how we handled the migration process, why we build a custom controller to handle broken nodes as well as how we have optimized our nodepools to avoid too frequent disruptions and much more
Marius, a dedicated DevOps Engineer at Hamburg’s fast-growing adtech company, adjoe. Since joining over three years ago, Marius has been on a mission to enhance the reliability and scalability of our backend — an event-driven microservice architecture written in Go and powered by Kubernetes. His passion for coding and Kubernetes doesn’t stop here. Marius also actively contributes to open-source projects, including CoreDNS and Karpenter, constantly pushing his skills and knowledge forward. When he’s not scaling systems or optimizing code, you’ll find him hosting board game nights, tackling bouldering walls, or setting off on adventures across Asia.
In high-scale environments, metrics cardinality isn’t just a resource concern, it’s an architectural challenge. Left unchecked, it can impact performance, query latency, and even system stability. This talk takes a deep technical dive into how VictoriaMetrics enables advanced observability practices with a strong focus on cardinality management. I’ll explore how to design efficient and scalable scrape configurations using Prometheus-compatible jobs and exporters, optimize your label strategies, and use built-in cardinality analysis tools within VictoriaMetrics to identify and mitigate high-cardinality patterns early. The session also covers integration with Grafana open source for visualizing metrics in a way that supports signal clarity and operational response, as well as setting up practical alerting strategies that minimize noise while ensuring fast issue detection. By the end of the talk, the audience will understand the engineering trade-offs of high-cardinality metrics and how to detect them, how VictoriaMetrics handles storage and querying at scale, how to build resilient and low-overhead scrape configs with Prometheus compatibility and how to use Grafana open source to highlight cardinality hot spots and improve alert signal quality.
Diana is a DX Engineer at VictoriaMetrics. She is passionate about Observability, machine learning. She is an active contributor to the OpenTelemetry CNCF open source project and supports women in tech.
Two Buzzwords Finally Meet! How should we manage AI in large organizations? What are the "services" developers need to add AI to enterprise apps, and what role do platform engineers take? Where do data scientists fit in? How does MCP, A2A, and whatever the latest AI API is fit in? There are so many questions because the field of managing AI in enterprises barely exists. We need to figure it out quickly however, before we see a repeat of a past patterns, like shadow AI and unmanageable apps in production. Based on real-world examples, this talk will go over what we currently know about using platform engineering to help developers use AI.
Michael Cote studies how large organizations get better at building software to run better and grow their business. His books Changing Mindsets, Monolithic Transformation, and The Business Bottleneck_ cover these topics. He's been an industry analyst at RedMonk and 451 Research, done corporate strategy and M&A, and was a programmer. He also co-hosts several podcasts, including Software Defined Talk. His daily-ish newsletter is at newsletter.cote.io.
Chaos Engineering is often misunderstood as simply “breaking things on purpose.” This talk challenges that perception and repositions Chaos Engineering as a critical pillar of reliability and resilience engineering. Rather than focusing on failure injection alone, we explore how to leverage existing knowledge, validate known truths, and foster confidence in complex systems.
In the first part, we deconstruct common myths around Chaos Engineering and reframe its core principles. Learn how aligning chaos practices with reliability goals can transform the way your organization perceives and applies these techniques—by emphasizing structured validation over blind experimentation.
The second part brings theory into practice with a hands-on framework that reimagines chaos experiments as self-feeding, iterative loops—mirroring the scientific method. We introduce the concept of continuous verification, drawing parallels with integration testing, and show how Chaos Engineering can seamlessly integrate into the Software Development Lifecycle (SDLC) through a shift-left approach.
The session wraps up with a visual framework for implementing a sustainable Chaos Engineering strategy, including how to evolve gamedays into repeatable, hypothesis-driven validations that scale with system changes.
Whether you're just exploring Chaos Engineering or looking to mature your reliability strategy, this talk will leave you with actionable insights, a modernized mindset, and a clear path to operational resilience.
I am a software engineer with an attrition for low-level and Linux internals who joined Datadog 7 years ago in the SRE group. After developing the now open-source Chaos Controller project meant to provide large-scale fault injection to engineering teams, I built the Security Chaos Engineering group now made of 3 teams and 20 people for which I act as the Engineering Manager. I am also part of the Core Incident Commanders group involved in all high severity outages to help with internal coordination and external communication.
