0.1 devopsdays-barcelona-2026 2026-11-13 2026-11-14 2 00:05 https://talks.devopsdays.org Europe/Madrid Bogatell Workshops (English) Workshops - 2hrs 2026-11-13T15:00:00+01:00 15:00 02:00 CPU and memory are the defaults for scaling up. But in many projects, these metrics react minutes late to issues caused by other areas of the application, thus delaying your autoscaling. In this workshop, we will learn how to hunt for the right metric and how to scale once you find it using Kind, Keda, and Prometheus. devopsdays-barcelona-2026-6802-it-s-too-late-to-scale-up-now-how-to-choose-the-right-metric-to-scale Christian Polanco en CPU and memory are the defaults for scaling up. But in many projects, these metrics react minutes late to issues caused by other areas of the application, thus delaying your autoscaling. In this workshop, we will learn how to hunt for the right metric and how to scale once you find it using Kind, Keda, and Prometheus. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/DSKA8T/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/DSKA8T/feedback/ Bogatell Workshops (English) Workshops - 2hrs 2026-11-13T17:30:00+01:00 17:30 02:00 Today we're generating more code than ever, but most teams aren't converting it into shipped, working, high-quality software. Delivering software is rarely a one-team activity—it's multiple teams coordinating, and most companies lack a practice to fix this systemic problem. Value Stream Mapping does exactly that. In this hands-on workshop, you'll map a real delivery workflow, measure the handovers, and leave with a prioritized plan to ship faster without sacrificing quality. devopsdays-barcelona-2026-6627-intro-to-value-stream-mapping-for-leaders Miguel Dias en In this hands-on session, you'll map and measure a real delivery workflow, identify bottlenecks, and apply lean principles to improve your delivery's speed and quality. The workshop distills 10+ hours of mapping exercises and two years of mapping experience into a practical, do-it-yourself format. Come with a delivery process in mind; leave with a concrete map and an action plan. Agenda: - Arrival and introductions - Overview of value stream mapping - Hands-on mapping exercise - Group discussion on constraints & solutions - Action planning & next steps false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/DER3ET/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/DER3ET/feedback/ Pallars Workshops (English) Workshops - 2hrs 2026-11-13T15:00:00+01:00 15:00 02:00 This beginner-friendly, three-hour hands-on workshop guides developers and SREs through instrumenting applications using OpenTelemetry and exporting telemetry data (metrics, logs, and traces) to the Grafana LGTM stack. Participants will explore various instrumentation approaches—including code-level OpenTelemetry SDKs, infrastructure metric collection via the Collector, and zero-code eBPF instrumentation for cross-service communication—alongside optimization techniques like span sampling and metrics tuning. By the end of the session, attendees will gain a clear, practical roadmap for implementing and customizing scalable observability patterns within their own Docker-based environments. devopsdays-barcelona-2026-6662-getting-started-with-opentelemetry-instrumentation-a-practical-playbook Mario MaciasMiguel Angel Ortega en OpenTelemetry has become an essential open source framework for standardizing telemetry data. In this beginner-friendly hands-on lab, you’ll walk through the journey of instrumenting an application with OpenTelemetry and sending metrics, logs, and traces to the Grafana LGTM stack (Loki for logs, Grafana for visualization, Tempo for traces, and Mimir for metrics). You’ll learn common instrumentation approaches, such as adding application-level telemetry using the OpenTelemetry SDK, collecting basic infrastructure metrics with the OpenTelemetry Collector, and implementing cross-service communication with zero-code eBPF instrumentation. You’ll also apply practical customization techniques, such as enriching and sampling spans, tuning metrics, and adding your own signals when auto-instrumentation isn’t enough. By instrumenting a sample application step by step, you’ll leave this lab with a clear roadmap for choosing the right OpenTelemetry instrumentation approach within your own environment. By the end of the three hours, you will: - Have a core understanding of the OpenTelemetry project and its key components - Select the right level of instrumentation based on various use cases - Understand how zero-code eBPF instrumentation helps reveal cross-service communication - Instrument applications using OpenTelemetry SDKs - Apply end-to-end instrumentation patterns to get started quickly and improve over time - Send telemetry to the Grafana LGTM stack and understand how it’s used - Customize telemetry to manage cost and noise Requirements: - Laptop with WiFi access - Linux/MacOS/WSL2 - Docker - Docker compose - Administrator or sudo access to build and run Docker containers - We will provide a docker-compose file containing what is needed for this lab. This session is tailored for developers and SREs. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/VYEFPG/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/VYEFPG/feedback/ Pallars Workshops (English) Workshops - 2hrs 2026-11-13T17:30:00+01:00 17:30 02:00 AI workloads are flooding onto Kubernetes, and most teams still hand-roll fragile YAML to run them. In this hands-on hour you'll build a small Kubernetes operator that manages an AI agent declaratively — turning a simple AIAgent custom resource into a running, self-healing app — and learn the watch-reconcile pattern behind real projects like KServe and KubeAI. devopsdays-barcelona-2026-6593-self-healing-ai-on-kubernetes-build-an-operator-for-your-llm-app Kritik Sachdeva en Running an AI app on Kubernetes usually means a pile of Deployments, Services, ConfigMaps and Secrets that someone maintains by hand. An operator replaces all of that with one declarative resource: you describe the agent you want, and the cluster keeps it running, configured, and healed. In this workshop you'll build that operator yourself. Starting from a provided skeleton, you'll define an AIAgent custom resource (its model, replicas, and config) and implement the controller that reconciles it: an informer that watches your AIAgent objects, a work queue, and a reconcile function that creates and maintains the underlying Deployment and Service running a lightweight local model. Then we make it earn the name "self-healing" — delete the agent's Deployment and watch the operator recreate it, bump the replica count and watch it scale, change the model field and watch it roll out. The sample agent runs on CPU against a local cluster (no GPU, no external API keys required), so everyone gets a working AI app on their own laptop. We'll close by mapping what you built onto how production AI operators handle the harder parts — GPUs, model storage, autoscaling. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/KAXXTX/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/KAXXTX/feedback/ Àvila Workshops (Spanish) Workshops - 2hrs 2026-11-13T15:00:00+01:00 15:00 02:00 When performance drops, most teams scale up by adding more resources, GPUs, and cost, often without real gains. In this session, we’ll show how to move from reactive scaling to a data-driven approach by understanding workload behavior and challenging misleading signals like CPU utilization. You’ll learn a practical framework to optimize performance, cost, and efficiency for your workloads. devopsdays-barcelona-2026-6110-tu-sistema-no-es-lento-lo-estas-midiendo-mal Guillermo Ruiz es Most performance issues are solved the same way: add more CPU, more memory, or scale out. It works... but it’s often an expensive shortcut that hides the real problem. In this session, we’ll explore a practical approach to performance engineering using open-source tools and reproducible methods. Instead of relying on intuition or single metrics like CPU usage, we’ll break down how to characterize workload behavior (CPU, memory, and I/O patterns), identify system limits through breaking-point testing, and measure efficiency using cost per unit of work. Through different examples, we’ll analyze how multiple workloads behave under load, why average latency is misleading, and how to detect the “knee of the curve” where systems begin to fail. We’ll also dive into hands-on optimization techniques (including memory-efficient patterns, caching strategies, and SIMD vectorization) showing how code changes can outperform infrastructure scaling. You’ll leave with... A clear mental model to understand your workload behavior A practical, repeatable framework you can apply immediately to decide when scaling is necessary...and when it’s just unnecessary spend. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/N9BX9T/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/N9BX9T/feedback/ Àvila Workshops (Spanish) Workshops - 2hrs 2026-11-13T17:30:00+01:00 17:30 02:00 Los pipelines de CI/CD tradicionales suelen ser demasiado rígidos para evaluar la experiencia de usuario real, limitándose a tests estáticos o ejecuciones pesadas de Lighthouse. En la era del Platform Engineering, podemos ir un paso más allá. Este taller práctico introduce el enfoque "Agent-First Design" aplicado al rendimiento web. Aprenderemos a construir y desplegar un flujo de trabajo donde agentes de IA, utilizando el Model Context Protocol (MCP), ejecutan herramientas de diagnóstico del navegador de forma determinista y autónoma. El asistente aprenderá a conectar un LLM local con scripts de WebPerf para auditar interacciones, identificar regresiones de rendimiento (LCP, CLS, LoAF) provocadas por cambios en el código, e integrar el veredicto del agente como un paso inteligente dentro del pipeline de despliegue. devopsdays-barcelona-2026-6533-multi-agent-performance-audits-automatizando-core-web-vitals-en-tu-plataforma-interna-con-mcp Joan Leon es **Requisitos técnicos e infraestructura del taller:** Para garantizar una experiencia fluida y sin fricciones durante las 2 horas de taller, la arquitectura está diseñada bajo los siguientes pilares: - Entorno 100% local y contenedorizado: Todo el ecosistema (aplicación de prueba, servidor MCP y automatización del navegador) corre bajo Docker. Los asistentes solo necesitan clonar el repositorio y ejecutar docker-compose up. - Sin dependencias externas ni APIs de pago: Para mitigar problemas de red y costes, el taller utiliza Ollama integrado en Docker con un modelo de código ligero _(qwen2.5-coder o similar)_ precargado en la fase de build. No se requiere ninguna API Key externa. - Entregable "Listo para Producción": El taller es completamente autoguiado mediante un repositorio estructurado paso a paso. Al finalizar, los asistentes se llevarán un entorno real y funcional que podrán replicar y adaptar a las plataformas de desarrollo de sus respectivas empresas al día siguiente. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/RREDSK/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/RREDSK/feedback/ Pujades Track (English) Keynote 2026-11-14T09:15:00+01:00 09:15 00:40 The 2026 open source ecosystem is facing a paradox of unprecedented scale. On one hand, autonomous AI agents are identifying decades-old vulnerabilities in critical infrastructure and auto-generating patches before threat actors can exploit them. On the other hand, maintainers are being crushed under a DDoS-like wave of security reports and code contributions that cost nothing to generate but demand hours of unpaid human labor to validate. In this keynote, we will explore how global open source communities are adapting to this asymmetric reality. We will look at the rise of the "found on my machine" AI-assisted bug report: complex, unexplainable, and nearly impossible to reproduce. More critically, we will tackle the architectural dilemma: what happens when an AI accurately flags a deep structural flaw, but the refactoring effort is completely out of reach for a volunteer team already strapped for time? While industry initiatives are attempting to pair AI discovery with human security triage to shield maintainers, the human-in-the-loop bottleneck remains a profound threat to project health. Finally, we will zoom out to address an existential shift in software engineering: the fading relevance of traditional licensing. When a developer can simply prompt Claude to build the exact bespoke tooling they need from scratch in seconds, the historical moats of the MIT or GPL licenses begin to evaporate. If the primary abstraction layer has moved from source code to plain-English intent, what does "open source" actually mean today? The primary case study will be the PostgreSQL project. Having worked with and in the project for the better part of 5 years, I have a unique insight into the conversation around adapting for the agents. devopsdays-barcelona-2026-6947-the-contribution-firehose-open-source-in-the-claude-era Floor Drees en The 2026 open source ecosystem is facing a paradox of unprecedented scale. On one hand, autonomous AI agents are identifying decades-old vulnerabilities in critical infrastructure and auto-generating patches before threat actors can exploit them. On the other hand, maintainers are being crushed under a DDoS-like wave of security reports and code contributions that cost nothing to generate but demand hours of unpaid human labor to validate. In this keynote, we will explore how global open source communities are adapting to this asymmetric reality. We will look at the rise of the "found on my machine" AI-assisted bug report: complex, unexplainable, and nearly impossible to reproduce. More critically, we will tackle the architectural dilemma: what happens when an AI accurately flags a deep structural flaw, but the refactoring effort is completely out of reach for a volunteer team already strapped for time? While industry initiatives are attempting to pair AI discovery with human security triage to shield maintainers, the human-in-the-loop bottleneck remains a profound threat to project health. Finally, we will zoom out to address an existential shift in software engineering: the fading relevance of traditional licensing. When a developer can simply prompt Claude to build the exact bespoke tooling they need from scratch in seconds, the historical moats of the MIT or GPL licenses begin to evaporate. If the primary abstraction layer has moved from source code to plain-English intent, what does "open source" actually mean today? The primary case study will be the PostgreSQL project. Having worked with and in the project for the better part of 5 years, I have a unique insight into the conversation around adapting for the agents. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/EYZDM8/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/EYZDM8/feedback/ Pujades Track (English) Talk 2026-11-14T10:00:00+01:00 10:00 00:25 We still hear, "OpenTelemetry (OTel) is vendor neutral so you can switch vendors any time you want to." This is akin to saying because the vCard format exists, it's easy to switch from iOS to Android. Yes, your core data will ultimately be portable, but you'll be missing a lot of other things. This doesn't make vendor neutrality moot. Switching vendors isn't like waving a magic wand, but it is much easier thanks to OTel. We’ll cover some of the challenges and pitfalls, and offer best practices to make this process as pain-free as possible. We’ll discuss: * OTel APIs/SDKs ease tool migration: helpful but not foolproof * OTel Collector enables multi-tool simulcast, ideal for vendor "bake-offs" * OpenTelemetry Protocol (OTLP): OTel’s standout feature * What's transferrable between vendors vs what's not Attendees will come away with an understanding of what OTel vendor neutrality means, so they can make informed decisions when considering switching to or adopting new tooling. devopsdays-barcelona-2026-6509-uncovered-the-hard-truth-about-opentelemetry-s-vendor-neutrality Josh Lee en Tool choices can shift with reorganizations or mergers. The fact that OpenTelemetry (OTel) is vendor neutral is a superpower…but what exactly does that vendor neutrality actually mean? OTel is designed such that even if you want to swap out OTel’s official SDK for your own, you still can, without breaking anything, as long as you implement the API. The OTel Collector is designed so that you can ingest telemetry data from multiple data sources and multiple formats, and export data using OTLP (OpenTelemetry Protocol) to any OTLP-compatible backend. The ability to mix-and-match OTel-compatible tools, and to pick and choose pieces of OpenTelemetry to adopt, means that build-vs-buy is no longer a binary choice, but a spectrum of choice. End-users are empowered to leverage multiple tools simultaneously, if that best suits their needs. Vendors are empowered to provide ergonomic enhancements on top of open standards. OpenTelemetry is vendor neutral on data ingest. This means that you can point your OTel Collector to two or more OTel-compatible backends. But once the data is ingested… Not all backends may support all 3 “main” OpenTelemetry signals (traces, logs metrics). For example, Jaeger only ingests Traces. Prometheus only ingests metrics. Tools may visualize OTel signals differently Dashboards and dashboard query languages vary across tools. For example, some use PromQL, some use their own proprietary query language, and some use SQL. Some tools optimize on structuring OTel data differently, which can affect pricing when switching to another tool. For example, some vendors encourage sampling. Some discourage sampling. Some encourage enhancing traces with attributes. Some may encourage adding span events to traces. The power of choice means that users can assemble the solution that works for them in pursuit of Observability's true promise: the ability to ask useful questions, get meaningful answers, and enable practitioners to act effectively on what they’ve learned. This talk will unpack OpenTelemetry’s vendor neutrality, and help decision makers and practitioners alike understand what’s truly vendor-neutral and what’s not, helping them select the right tools for their own purposes, and to help them avoid those nasty surprises that come in the form of giant bills, giant learning curves, and interminable migration timelines. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/WZ9WXY/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/WZ9WXY/feedback/ Pujades Track (English) Talk 2026-11-14T10:30:00+01:00 10:30 00:25 Operating systems at massive scale means designing for failure, traffic spikes, and constant change. In this talk, I’ll share lessons from building and running distributed systems at companies like Canva and Slack, focusing on resilience, high availability, incident response, and SRE practices. Expect real-world examples of what breaks at scale—and how to design systems that survive it. devopsdays-barcelona-2026-5990-lessons-from-building-at-massive-scale Javier Turégano en Building software at massive scale means designing systems that don’t just work—but continue to work under extreme load, unpredictable traffic spikes, and constant change. In this talk, I’ll share lessons from building and operating distributed systems at companies like Canva and Slack, where platforms handle trillions of requests and support millions of users in real time. We’ll focus on what it actually takes to design for resilience and reliability in high-pressure environments. We’ll cover topics such as: - Designing for high availability and graceful degradation - Handling traffic spikes and load asymmetry without cascading failures - Evolving architectures as scale and complexity grow - Real-world incident response: what breaks, why, and how to recover fast - Applying SRE practices to keep systems reliable at 24x7 global scale This is a practical, experience-driven talk focused on the realities of operating systems at scale—where failure is inevitable, and resilience is designed. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/PN3YNG/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/PN3YNG/feedback/ Pujades Track (English) Talk 2026-11-14T11:30:00+01:00 11:30 00:25 Performance is a feature, yet it's often the first thing to break. Have you ever shipped a 'perfect' update, only to find your metrics tanked in production? Fixing regressions after deployment is a costly, manual nightmare that burns time and kills conversion. Stop playing whack-a-mole with your Core Web Vitals. In this session, we’ll move beyond manual checks and integrate automated performance testing directly into your CI pipeline. Learn how to catch bottlenecks before they hit your users, shift performance left, and transform your deployment process from a high-stakes gamble into a predictable, stress-free routine. devopsdays-barcelona-2026-6577-not-on-my-watch-catching-web-performance-disasters-in-ci Estela Franco en In this deep dive, we will explore the 'Not on my watch!' philosophy: building a robust, automated defense against performance regressions. We will cover: - The architectural impact of performance drift in modern web stacks. - How to implement automated performance gates within CI/CD pipelines using GitHub Actions, Lighthouse CI, and Lighthouse CL Server. - Distinguishing between 'lab data' and 'real-user data' when setting up automated thresholds. - Reducing friction in the developer experience: giving feedback early enough to prevent bad code from ever reaching the main branch. Attendees will leave with a clear, actionable framework to set up their own testing infrastructure, minimize production incidents, and foster a culture of performance-first development. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/KHZTA3/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/KHZTA3/feedback/ Pujades Track (English) Talk 2026-11-14T12:00:00+01:00 12:00 00:25 A real project story about introducing AI agents, reusable prompts, templates, and retrieval into the delivery lifecycle, from backlog refinement to planning and coding, while keeping humans in control. devopsdays-barcelona-2026-6565-from-backlog-to-pull-request-building-an-ai-augmented-development-lifecycle Fabio Scagliola en Many teams lose time in the space between business intent and working software. Backlog items arrive with missing context. Refinement creates clarification loops. Estimation happens before technical implications are fully understood. New joiners depend heavily on senior developers. Developers use AI tools individually, but without a shared process, reusable assets, or measurable delivery impact. This talk presents a real initiative to introduce an AI-augmented development lifecycle into a product team. The goal was not to replace developers or automate delivery end to end. The goal was to improve the flow from backlog item to refined work, from refined work to implementation plan, and from implementation plan to code, while keeping ownership, decision making, and accountability with the team. The first phase introduced an agentic development lifecycle with reusable agents, skills, prompts, templates, and working examples. A refinement agent helps improve clarity, completeness, acceptance criteria, and missing information. A planning agent helps identify dependencies, technical implications, blockers, risks, and estimation inputs. A coding agent uses the implementation plan, the codebase, and team conventions to support code generation and modification. At each step, the human remains in the loop, challenging the output, adjusting it, and validating whether it makes sense. The second phase strengthens the lifecycle with a custom retrieval augmented generation capability for codebase and knowledge access. The idea is to ingest product requirements, software requirements, design specifications, logs, manuals, operational documentation, and source code, then expose this knowledge to both people and agents. With Graph RAG, for example, relationships between code, requirements, business rules, data, and runtime behavior can become easier to explore. A chat interface can make the same knowledge accessible to developers, business analysts, quality engineers, product owners, subject matter experts, and new joiners, regardless of which delivery or development tools they use. The talk will cover the lifecycle design, the human-in-the-loop workflow, the role of reusable prompts and skills, the relationship between agents and retrieval, and the measurement approach. Candidate KPIs include cycle time from ready to done, backlog items completed per sprint, carry over, estimation accuracy, time to find reliable information, onboarding time, repeated questions to senior developers or subject matter experts, token consumption or AI cost per completed backlog item, and avoidable rework. Attendees will leave with a practical model for introducing AI into delivery without treating it as magic, a black box, or a vendor demo. The main takeaway is that AI can improve delivery when it is embedded into team practices, grounded in real context, measured with discipline, and designed to augment people rather than bypass them. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/HSBNDT/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/HSBNDT/feedback/ Pujades Track (English) Talk 2026-11-14T12:30:00+01:00 12:30 00:25 Most engineering organizations want autonomous teams. In smaller systems, that often works well: teams coordinate directly, feedback is fast, and local decisions stay local. Strong communication happens because the system is still understandable. As systems grow, though, feedback loops slow down, integrations become harder to reason about, and changes become expensive to reverse. Teams that once moved independently suddenly need standards, platform constraints, and coordination just to keep things reliable. Communication starts breaking down, long before the systems do. Using examples from platform migrations, this talk explores why organizations drift between uncontrolled autonomy and excessive governance and how both can quietly reduce delivery effectiveness. You’ll leave with practical ways to spot early coordination signals, recognize when architecture needs to become more explicit, and start better cross-team conversations without needing to be a manager, architect, or scrum master. devopsdays-barcelona-2026-6257-flocks-vs-pyramids-when-self-organization-stops-working /media/devopsdays-barcelona-2026/submissions/DNTRXX/image_U1ggh2I.webp Jos van Schouten en This talk is aimed at engineers, tech leads, and platform teams dealing with growing coordination complexity between teams. It’s less about a specific framework (like Team Topologies) and more about recognizing the environmental conditions that change how teams collaborate as systems scale. While it touches on themes like autonomy, governance, and architecture, the goal is to help attendees recognize early coordination and communication signals especially if they’re not in formal leadership or architecture roles. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/DNTRXX/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/DNTRXX/feedback/ Pujades Track (English) Ignite Talks 2026-11-14T13:00:00+01:00 13:00 00:05 GitOps promises simplicity, consistency, and automation, but without discipline, it can just as easily invite drift, outages, and operational pain. GitOps is not a "set it and forget it" solution; it's a living, breathing system that requires ongoing maintenance and nurturing over time. In this talk, you will learn about the pitfalls of not caring about best practices in GitOps through real-world examples and lessons learned. Whether you're new to GitOps or scaling an enterprise platform, this talk will help you spot warning signs early, avoid painful mistakes, and strengthen your GitOps practices with confidence. devopsdays-barcelona-2026-6288-the-7-deadly-sins-of-gitops Koray Oksay en We will cover sins such as pride (ignoring drift), envy (Blindly copying other GitOps setups), sloth (ignoring reconciliation errors), and others, as well as practical fixes and patterns that teams can apply to build more resilient and sustainable workflows. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/8GWQSV/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/8GWQSV/feedback/ Pujades Track (English) Ignite Talks 2026-11-14T13:05:00+01:00 13:05 00:05 Is your team’s health as observable as your software? The very traits we celebrate in high-performing teams (speed, grit, and commitment) are the exact variables that lead to burnout. It’s not a paradox; it’s a design flaw. This talk explores how to stop 'fixing' the people and start engineering the system, treating human bandwidth as a finite technical constraint rather than a soft skill. devopsdays-barcelona-2026-6659-burnout-the-hidden-failure-mode-of-high-performing-teams Diana Nanuti en Is your team’s health as observable as your software? High-performing engineering teams are celebrated for their velocity and "whatever it takes" commitment. Yet, these same traits often make them the most vulnerable to a predictable, systemic failure mode: burnout. This isn’t a lack of individual grit; it’s a design flaw. When we architect software for 99.9% uptime but run our teams at 100% capacity, we create a system with zero fault tolerance. In this talk, we move beyond the superficial "resiliency" narrative and analyze team health through the lens of systems engineering. We will explore how to apply SRE principles (like load shedding, redundancy mechanisms, and leading indicators) to the human element of the stack. You’ll learn why "idle capacity" is the secret to low latency, how to make cognitive load visible, and how to build a system where high performance doesn't require a "hero culture" destined for a catastrophic outage. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/XFNSAB/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/XFNSAB/feedback/ Pujades Track (English) Ignite Talks 2026-11-14T13:10:00+01:00 13:10 00:05 Modern DevOps has moved beyond automation. We’re now building systems that operate with increasing autonomy. With AI‑assisted platforms and intelligent workflows entering the stack, engineering teams are asking their systems to do more than execute tasks. They are asking them to decide. But what happens when those decisions are wrong? In this fast-paced Ignite talk, I’ll share real-world lessons from building and enabling modern automation workflows, including where autonomy breaks down, how small assumptions cascade into systemic issues, and why “safe automation” is more fragile than it appears. Drawing on practical experiences with AI-assisted DevOps systems, this talk highlights the gap between what automation promises and what production reality delivers. This is not a talk about why automation is good or bad. It is about what changes after it works and why that is where the real engineering challenges begin. You’ll walk away with: A new mental model for thinking about automation vs autonomy A recognisable pattern behind silent system failures A practical way to design systems that fail visibly, not invisibly If you’ve ever trusted a system because “it usually works,” this talk will make you question why. devopsdays-barcelona-2026-6418-from-manual-to-autonomous-what-breaks-when-you-automate-everything Saikeerthi M en We set out to automate everything. We never stopped to ask what happens after. As DevOps systems evolve into autonomous, AI‑assisted workflows, failure doesn’t disappear — it changes shape. It becomes quieter, subtler, and far more dangerous. The real risk is no longer the system that breaks, but the one that continues to run… incorrectly and unnoticed. This Ignite talk explores the hidden failure modes of modern automation: where “safe automation” quietly breaks, where assumptions go unchallenged, and where removing humans from the loop shifts — not eliminates — responsibility. Because in a world of autonomous systems, the hardest failures to catch are the ones that look like everything is working. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/C87ESF/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/C87ESF/feedback/ Pujades Track (English) Ignite Talks 2026-11-14T13:15:00+01:00 13:15 00:05 Modern security teams are drowning in alerts while attackers increasingly automate reconnaissance and exploitation. This Ignite explores why a well-placed honeypot assets can provide a higher-confidence signal than thousands of traditional security alerts, especially against the AI-powered attacks devopsdays-barcelona-2026-6421-one-fake-password-is-worth-more-than-10-000-alerts Ilia Dubovskii en Security teams have become exceptionally good at generating alerts. Attackers have become exceptionally good at generating noise. As AI-powered tooling lowers the cost of reconnaissance and exploitation, defenders face an uncomfortable reality: more detection does not always mean better detection. This talk argues that high-confidence signals matter more than ever. Using examples from honeypots, canary credentials, decoy files, and deception techniques, we’ll explore why a single interaction with a fake secret can provide more actionable intelligence than thousands of low-confidence alerts. Rather than asking what an attacker could do, deception technologies focus on detecting what an attacker actually did. The result is fewer alerts, higher confidence, and faster response. Key Takeaways: * Why alert volume is becoming a liability. * How deception technologies work in modern environments. * Why AI-assisted attacks increase the value of honeypots. * The difference between exposure-based and intent-based detection. * Practical ideas for implementing low-cost deception techniques. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/WL8Z77/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/WL8Z77/feedback/ Pujades Track (English) Ignite Talks 2026-11-14T13:20:00+01:00 13:20 00:05 Carcinisation is a form of convergent evolution where non-crab entities form crab-like adaptations in an effort to increase their chances of survival. While this evolutionary strategy is widely successful, there are a few fail states with AI technologists should be careful to avoid. devopsdays-barcelona-2026-6595-the-carcinisation-of-ai ecology_chris en The jump from Claude to clawdbot, and finally open claw heralded the carcinisation of AI. While crablike adaptations have been successful evolutionary strategy for millions of years and has some early success with AI technology, the humans in the system should be mindful of their crabbiness, especially when it isn't being useful. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/VQW9MB/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/VQW9MB/feedback/ Pujades Track (English) Open Space 2026-11-14T15:30:00+01:00 15:30 00:30 Open Space 1 devopsdays-barcelona-2026-7147-open-space-1 en Open Space 1 false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/Z9L8GU/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/Z9L8GU/feedback/ Pujades Track (English) Open Space 2026-11-14T16:30:00+01:00 16:30 00:30 Open Space 2 devopsdays-barcelona-2026-7148-open-space-2 en Open Space 2 false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/YW8EKY/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/YW8EKY/feedback/ Llacuna Track (English) Talk 2026-11-14T10:00:00+01:00 10:00 00:25 Platform Engineering is often presented as a problem of tooling: self-service platforms, golden paths, developer portals and automation. Those capabilities are important, but in my experience they are rarely the limiting factor. At Cabify we found that most platform initiatives had a reasonable justification behind them. Reliability improvements, developer experience, compliance requirements, cost optimization and new capabilities all created value. The challenge was not deciding what was worth doing, but deciding what was worth doing first. This talk shares lessons learned from running infrastructure and platform teams where the number of worthwhile opportunities consistently exceeded available capacity, and how that changed our approach and processes to Platform Engineering. devopsdays-barcelona-2026-6568-the-hardest-platform-problems-weren-t-technical Abel Navarro en Platform Engineering is often presented as a problem of tooling. The discussion usually revolves around self-service capabilities, golden paths, developer portals, automation and developer experience. Those capabilities are important and we invest in many of them ourselves, but over the last few years I have come to believe that they are rarely the limiting factor. In my experience, platform teams do not suffer from a lack of ideas. The opposite is usually true. Reliability improvements, developer experience initiatives, compliance requirements, cost optimization, technical debt reduction and new platform capabilities can all have a reasonable business case behind them. The difficulty is that they all compete for the same limited capacity. At Cabify we have been trying to evolve from infrastructure as a collection of services towards Platform Engineering with a stronger product mindset. That journey has been useful because it helped make some of these tensions more visible. We found ourselves spending less time discussing how to implement things and more time discussing why we should implement them, what value they would create and what other work would be displaced as a consequence. As the number of opportunities grew, we started experimenting with different approaches to prioritization. We introduced a single backlog for Platform, moved discussions upstream, explored Internal Product Advocates (IPAs) and tried to make value and expected outcomes more explicit. None of these approaches magically solved the problem, but they helped create better conversations around trade-offs and priorities. In this talk I will share examples from infrastructure and platform work, including operational improvements, reliability initiatives, governance requirements and developer experience investments. The goal is not to present a prioritization framework or claim that we found the answer. Rather, I want to discuss a challenge that I suspect many platform teams face: how do you make decisions when most of the available options are worthwhile and there is never enough capacity to do all of them? My hope is that attendees leave with a different perspective on Platform Engineering. Beyond the technology, the tooling and the automation, there is an ongoing exercise in deciding where to invest limited capacity. Those decisions shape the platform at least as much as any architectural choice, yet they receive far less attention in our industry discussions. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/QRKUEB/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/QRKUEB/feedback/ Llacuna Track (English) Talk 2026-11-14T10:30:00+01:00 10:30 00:25 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. This is an entry level talk that requires little previous knowledge. The audience will get a general idea of the obstacles and challenges of applying DevOps practices in a New Space company. devopsdays-barcelona-2026-6519-devops-in-space-lessons-from-low-earth-orbit David Jacovkis en The Infrastructure & Software Engineering team at Sateliot works at the intersection of aerospace, telecommunications and software. We build modern distributed systems and then send them to an extremely harsh 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, strong regulation and the cultural gaps between very different fields of engineering. I'll also share the ways we have found within those constraints to apply some of the DevOps processes and tools that have become industry standards. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/QKVH33/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/QKVH33/feedback/ Llacuna Track (English) Talk 2026-11-14T11:30:00+01:00 11:30 00:25 Every new SQL database at Mews used to mean a ticket to the Platform team. No controls, no standards, no audit. We didn't even know who had prod access. Here's how we fixed that - for 187 servers, 400+ engineers, and an AI era where everyone is a builder. devopsdays-barcelona-2026-6571-access-without-chaos-sql-guardrails-when-everyone-s-a-builder /media/devopsdays-barcelona-2026/submissions/ZTQYMS/image_ZaqrXh4.webp Carlos Augusto Pega en Mews had grown organically for over a decade through product-market fit and scale stages without any effective SQL access governance. So it was that we came to this problem with a chaotic mess of access and permissions across our databases. We didn't exhibit least privilege, there was no logging of access, and no shared standards. In many cases, it was guesswork on who had access to each database. That was the problem worth solving. The solution came together in layers. We built a centralised Terraform repository as the single source of truth for SQL access configuration. We introduced a PIM self-service model where engineering managers and staff engineers manage their own teams' database memberships - no Platform team involvement needed at runtime. 400+ engineers now operate within a zero-standing-access model: time-limited, justified, fully auditable. Connection strings and local users gave way to managed identity authentication throughout the fleet. Three cloud-native policies now enforce compliance at the control plane level - resource locks preventing accidental deletion, identity administrator governance, and audit logging routed to a centralised store. These aren't conventions or recommendations. Teams cannot remove or override them. The shared Terraform SQL module provides opinionated defaults that land compliant from day one, but it's the policy layer that makes compliance permanent. New services can't drift even if they try. In 2026, with AI tools enabling everyone - engineers, analysts, and non-technical contributors - to spin up infrastructure and access production data, the blast radius of poor access hygiene has never been wider. Carlos will walk you through the full journey - from the first Terraform commit to production-enforced cloud policies - including what broke along the way, what we over-engineered the first time, and the organisational side of handing access ownership back to product teams. **You'll leave with:** - A blueprint for self-service database access using just-in-time privilege elevation and identity provider groups - A clear picture of how cloud-native policy enforcement makes compliance immutable - not just recommended - Honest lessons from the rollout: what broke, what surprised us, and the org change management side of removing the Platform team from the critical path - A framework for thinking about access guardrails in the AI era - where anyone can become a data consumer, and the blast radius of poor governance has never been wider This talk is for platform engineers, DevSecOps practitioners, and anyone who has ever found themselves as the bottleneck on access governance. _No access requests were harmed in the making of this talk._ false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/ZTQYMS/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/ZTQYMS/feedback/ Llacuna Track (English) Talk 2026-11-14T12:00:00+01:00 12:00 00:25 Software development is not just about writing code, but also about how our brains handle complexity, learning, and problem-solving under pressure. Why does a day of coding feel so mentally exhausting? Why do solutions appear when you step away from your desk? And why do we sometimes get stuck chasing the wrong bug for hours? In this talk, we explore the intersection of neuroscience and programming through four practical concepts: your brain’s “background processor,” its ability to rewire itself, the limits of working memory, and how cognitive biases affect debugging. You’ll leave with a simple, actionable toolkit to avoid common mental traps, learn faster, and code more effectively. devopsdays-barcelona-2026-6003-the-developer-s-brain-cognitive-science-for-better-code Marina Altés en If you’re a developer, your most important tool is not your editor or your setup but your brain. And yet, most people don't know much about how it actually works. This talk is a practical introduction to the cognitive side of software engineering. We’ll explore why coding is so mentally demanding and how understanding a few key mechanisms of the brain can significantly improve the way we work. Through real-world examples and relatable scenarios, we’ll cover four essential concepts: 1. The brain’s background processor - Zooming in vs zooming out - How to trigger the "a-ha" moments 2. Neuroplasticity - What happens in the brain when we learn new technologies - What's the most optimal strategy to learning 3. Cognitive load - Why complex code quickly becomes overwhelming - Techniques to manage mental load through decomposition and externalization 4. Biases - The brain as a pattern recognition machine - A bias-resistent approach to debugging and problem-solving We’ll finish by combining these ideas into a practical cognitive toolkit you can apply immediately in your day-to-day work. This isn’t a theory-heavy talk, but rather some practical guidelines to building a cognitive toolkit you can apply immediately in your day-to-day work so you can write better code, make better decisions, and work more sustainably. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/WNP8ZE/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/WNP8ZE/feedback/ Llacuna Track (English) Talk 2026-11-14T12:30:00+01:00 12:30 00:25 Many incident processes optimize for compliance, not humans. This talk explores how blending DevOps principles with modern ITIL practices can reduce burnout, improve recovery, and create healthier engineering cultures. devopsdays-barcelona-2026-6342-extra-crispy-your-incident-process-is-burning-out-your-engineers /media/devopsdays-barcelona-2026/submissions/WKDJVB/image_CdHt34t.webp Chris Ward en At 2:13 AM, nobody cares whether your incident process is technically compliant. They care whether people know what to do, whether communication is clear, and whether the same exhausted engineer has become the single point of failure for your entire company. For years, many organizations treated ITIL and DevOps as enemies: one focused on control, the other on speed. But after working with engineering and operations teams across multiple environments, I discovered the real problem wasn’t process, it was designing systems that ignored the humans inside them. In this talk, I’ll share real-world lessons from teams struggling with alert fatigue, endless escalations, hero culture, and burnout disguised as “ownership.” We’ll explore how modern ITIL concepts like continual improvement, incident management, and value streams can actually support DevOps practices when implemented with empathy instead of bureaucracy. ## Attendees will learn: - Why “hero culture” silently destroys operational resilience - How poorly designed escalation paths increase burnout - What psychologically safe incident response actually looks like - Where ITIL still provides value in modern DevOps organizations - Practical ways to reduce operational stress without sacrificing reliability false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/WKDJVB/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/WKDJVB/feedback/ Llacuna Track (English) Open Space 2026-11-14T15:30:00+01:00 15:30 00:30 Open Space 3 devopsdays-barcelona-2026-7149-open-space-3 en Open Space 3 false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/8GQAKJ/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/8GQAKJ/feedback/ Llacuna Track (English) Open Space 2026-11-14T16:30:00+01:00 16:30 00:30 Open Space 4 devopsdays-barcelona-2026-7150-open-space-4 en Open Space 4 false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/BXVXCB/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/BXVXCB/feedback/ Rambla Track (Spanish) Talk 2026-11-14T10:00:00+01:00 10:00 00:25 El auge de la IA Generativa ha creado un dilema para los equipos de infraestructura y operaciones: los desarrolladores necesitan moverse rápido, pero enviar información sensible a APIs de LLMs públicos puede romper políticas de soberanía de datos y complicar los controles de costes de la nube con facturas impredecibles. ¿La solución? Traer la IA a tus propios datos. En esta charla, exploraremos cómo construir una plataforma interna de IA basada en open-source y "air-gapped" en Kubernetes. Descubre cómo combinar modelos abiertos (Gemma 4), bases de datos vectoriales (PostgreSQL con pgvector) y Model Context Protocol (MCP) para empaquetar un entorno seguro. Aprenderás cómo los equipos de Platform Engineering pueden ofrecer despliegues de IA en formato "autoservicio", garantizando la seguridad de los datos corporativos y transformando los costes variables de las APIs en costes de infraestructura predecibles. devopsdays-barcelona-2026-6580-genai-in-a-box-construyendo-una-plataforma-de-ia-en-kubernetes Miguel Toscano es Diseñada para SREs e Ingenieros de Plataforma, esta sesión busca abordar la realidad de operar IA en producción dentro de una plataforma automatizada abordando: - FinOps y Soberanía: Alternativas viables a las APIs SaaS para cargas de trabajo sensibles y agentes autónomos de alto consumo. - Arquitectura en K8s: El LLM (Gemma) como carga stateless, Model Context Protocol (MCP) para integración segura, y PostgreSQL como motor stateful. - Operando Postgres + pgvector en K8s: Cómo gestionar los picos de recursos (CPU/RAM) que introducen las búsquedas vectoriales para evitar la inestabilidad del clúster, y cómo automatizar el almacenamiento persistente. - Platform Engineering (GitOps): Cómo empaquetar toda esta complejidad bajo un enfoque declarativo para ofrecer entornos de IA aislados en formato "autoservicio" a los desarrolladores en cuestión de minutos. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/UMTHCM/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/UMTHCM/feedback/ Rambla Track (Spanish) Talk 2026-11-14T10:30:00+01:00 10:30 00:25 Los entornos tech imponen alta carga cognitiva, afectando el rendimiento y la salud. Esta charla presenta, desde experiencias reales, cómo impacta el cerebro y comparte estrategias prácticas para promover bienestar y rendimiento sostenible. devopsdays-barcelona-2026-5991-codigo-y-cerebro-salud-y-rendimiento-en-entornos-tecnologicos-de-alta-demanda-cognitiva Dri CardosoJoão Brito es Los entornos tecnológicos, especialmente en contextos de DevOps y comunidades open source, requieren cambios constantes de contexto, multitarea y exposición continua a altos niveles de carga cognitiva. Esto impacta directamente la atención, la toma de decisiones, el rendimiento y la salud mental. La charla se basa en experiencias reales con profesionales y comunidades tech, donde se observan patrones recurrentes: fatiga mental, sobrecarga, dificultad de concentración, inestabilidad en el rendimiento y aumento de vulnerabilidades en el trabajo diario. Desde la neurociencia aplicada, se analiza cómo la carga cognitiva, las interrupciones, la presión por entregas y el exceso de información afectan las funciones ejecutivas y el comportamiento. Más allá de la teoría, la sesión propone aplicación práctica. Se presentan estrategias utilizadas en contextos reales, como técnicas de regulación cognitiva, organización del trabajo y construcción de entornos más sostenibles. También se discute cómo la cultura y la dinámica de los equipos pueden amplificar o reducir estos efectos. La sesión se realizará en inglés y español, promoviendo el intercambio entre participantes. Se invita a compartir experiencias y construir colectivamente estrategias para el cuidado y el rendimiento sostenible. Esta charla fue presentada en KubeCon Europe 2026 (Ámsterdam) y en eventos DevOps en Brasil (Salvador y Florianópolis, 2025), formando parte de una trayectoria de participación en casi 30 eventos tecnológicos desde 2022. Público objetivo: profesionales de tecnología, comunidades open source, líderes técnicos y equipos de alto rendimiento en entornos de alta demanda cognitiva. Formato: charla interactiva con espacio para la aplicación de ejercicios de regulación neurocognitiva. Ejes principales: Carga cognitiva y funcionamiento cerebral Impactos en la salud y el rendimiento en tecnología Estrategias prácticas de regulación neurocognitiva y organización del trabajo Construcción de entornos sostenibles e inclusivos Diferencial: integración entre neurociencia aplicada, experiencia práctica en comunidades tech y enfoque orientado a la implementación real. Adaptación: la charla amplía la teoría hacia actividades prácticas de salud. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/CSQ3R7/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/CSQ3R7/feedback/ Rambla Track (Spanish) Talk 2026-11-14T11:30:00+01:00 11:30 00:25 Los equipos DevOps modernos no carecen de datos; carecen de contexto operacional unificado. Esta charla comparte nuestra experiencia introduciendo _AI-assisted incident investigations_ en un entorno global de e-commerce. Exploraremos cómo la IA puede correlacionar información de Kubernetes, AWS, Argo CD, plataformas de observabilidad, repositorios e historial de deployments para ayudar a tomar decisiones más rápidas y mejor fundamentadas. También abordaremos los safeguards esenciales: read-only access, validation, auditability, stopping conditions y human oversight, incluyendo qué funcionó, qué falló y qué tareas operacionales deberían seguir siendo determinísticas. devopsdays-barcelona-2026-6630-de-los-dashboards-a-las-decisiones-integracion-de-ia-en-operaciones-devops-a-gran-escala /media/devopsdays-barcelona-2026/submissions/KA7ZWQ/image_0VrNe5w.webp JOSE JULIAN ARIZA V. es Modern DevOps teams rarely suffer from a lack of data. **The real problem is fragmentation.** During an incident, engineers may need to move between **Kubernetes, AWS, Argo CD, observability platforms, CI/CD pipelines, repositories, edge services, and internal documentation**. Each system provides part of the answer, but reconstructing the full operational story still requires time, experience, and repeated manual investigation. This talk presents our experience introducing **AI-assisted operational workflows** into a global e-commerce environment running distributed services across multiple platforms and environments. Rather than using AI only to generate commands or summarize logs, we explored how it could act as an **investigation layer across existing DevOps systems**: collecting context, correlating events, proposing hypotheses, and helping engineers move from raw telemetry to an informed operational decision. ### What the session will cover - The operational challenges of a **large-scale e-commerce platform** with multiple services, environments, deployment pipelines, and observability tools. - How operational context can be gathered from **Kubernetes, AWS, Argo CD, monitoring platforms, repositories, and deployment history**. - How an AI-assisted investigation loop can **plan actions, call read-only tools, evaluate observations, and refine its hypothesis**. - Why **deterministic workflows and AI agents** solve different categories of operational problems. - How we introduced **access controls, environment boundaries, auditability, stopping conditions, and human approval points**. - What failed during implementation, including **incomplete context, misleading correlations, excessive tool calls, and confident but incorrect conclusions**. - How tracing and evaluation helped us understand whether the system was actually improving incident investigation. - Which tasks proved useful for AI assistance and which remained safer and more reliable as traditional automation. A central theme of the talk is that **connecting a language model to operational tools is the easy part**. The difficult part is designing a system that knows: 1. What it is allowed to inspect. 2. How to validate what it finds. 3. When to stop. 4. When to defer to an engineer. The session will include a **practical architecture**, an example incident-investigation flow, the controls required for enterprise use, and the lessons we learned while applying these ideas in a real production environment. ### Key takeaways Attendees will leave with: - A realistic framework for deciding where AI can add value in DevOps. - A clearer understanding of where deterministic automation remains the better choice. - Practical guidance on the technical safeguards required before introducing agents into operational workflows. - Lessons learned from applying AI-assisted investigation in a real enterprise environment. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/KA7ZWQ/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/KA7ZWQ/feedback/ Rambla Track (Spanish) Talk 2026-11-14T12:00:00+01:00 12:00 00:25 La infraestructura ya se gestiona como código, pero los accesos siguen dependiendo de tickets y procesos manuales. Esta charla muestra cómo aplicar principios GitOps a la gobernanza de identidades y permisos. devopsdays-barcelona-2026-6416-entitlements-as-code-gobernanza-de-accesos-para-la-era-cloud-native Edu Borrego es Las organizaciones cloud-native han adoptado prácticas declarativas para infraestructura, despliegues y políticas, pero la gestión de accesos sigue dependiendo a menudo de tickets, procesos manuales y conocimiento tribal. Esta charla presenta Entitlements as Code: una forma de gestionar usuarios, grupos y membresías como estado deseado en Git, usando Entra ID como hub de identidad y un reconciler como Crossplane para alinear continuamente la definición declarativa con la realidad. A través de una evolución práctica, veremos cómo pasar de un repositorio versionado a capas de autoservicio mediante scripts, portales, formularios o asistentes de IA, sin romper el flujo de revisión, aprobación y auditoría. Los asistentes entenderán cómo reducir cuellos de botella, eliminar dependencias de personas concretas y construir un modelo de gobernanza de accesos más trazable, escalable y sostenible. false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/VWTFSC/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/VWTFSC/feedback/ Rambla Track (Spanish) Talk 2026-11-14T12:30:00+01:00 12:30 00:25 Nuestra plataforma procesa grandes volúmenes de eventos usando Kafka como almacén centralizado, y lo que comenzó siendo una arquitectura relativamente sencilla con algunos consumidores escribiendo sobre una base de datos MySQL compartida, fue evolucionando a medida que aumentaba el volumen de eventos Para evitar los cuellos de botella de la base de datos principal, los consumidores se fueron moviendo a bases de datos independientes a la vez que fueron apareciendo distintos servicios agregadores encargados de recopilar y consolidar la información distribuida para construir una visión global de los datos. Cada una de estas escisiones resolvía un problema de saturación o lentitud, pero con el tiempo terminamos administrando más de 20 bases de datos y múltiples procesos de agregación, con una complejidad creciente tanto a nivel operativo como de mantenimiento. Consultas que deberían resolverse en segundos podían requerir horas de procesamiento En esta charla compartiremos cómo rediseñamos la plataforma utilizando Kafka Connect y ClickHouse como núcleo de la capa analítica sin abandonar Kafka. Explicaremos la evolución de la arquitectura, los retos encontrados durante la migración y las lecciones aprendidas. Como resultado, conseguimos soportar picos de hasta 2 millones de mensajes procesados por segundo, podemos hacer consultas prácticamente en tiempo real y hemos simplificado de forma significativa la operación del sistema Pero esta historia no trata únicamente de tecnología. También hablaremos de cómo la creación de un equipo sólido, la adquisición progresiva de conocimiento y la construcción de una visión compartida fueron elementos fundamentales para afrontar una transformación de este calibre. Porque las arquitecturas evolucionan, pero son las personas quienes hacen posible el cambio devopsdays-barcelona-2026-6557-kafka-a-escala-como-pasar-de-un-mapa-de-metro-a-una-arquitectura-simplificada Esther Yébenes es Esta charla presenta la evolución real de una plataforma de procesamiento de eventos que fue creciendo durante años hasta que la complejidad operativa se convirtió en uno de los principales problemas a resolver. La arquitectura original estaba basada en Kafka y una base de datos MySQL compartida donde persistían datos los distintos consumidores. A medida que aumentó el volumen de eventos, la base de datos central empezó a convertirse en un cuello de botella, así que se optó por distribuir la carga creando bases de datos independientes para distintos consumidores. Esta solución funcionó durante bastante tiempo y permitió continuar escalando la plataforma y absorver más volumen de eventos. Sin embargo, cada nueva necesidad acababa incorporando nuevas bases de datos, nuevos procesos de agregación y nuevos puntos de integración. Lo que inicialmente era una optimización razonable terminó derivando en un ecosistema formado por más de 20 bases de datos y múltiples servicios agregadores encargados persistir los datos en la base de datos principal. Con el paso del tiempo empezaron a aparecer problemas que probablemente resulten familiares para muchos equipos, por ejemplo los costes operativos derivados de esta infraestructura, la dificultad en la gestión o las dependencias cruzadas entre sistemas, e incluso limitaciones que impactaban gravemente en negocio. Para resolver esta situación decidimos replantear la arquitectura y construir una plataforma analítica centralizada basada en Kafka, Kafka Connect y ClickHouse Durante la sesión hablaremos de - cómo evolucionó la arquitectura original - qué problemas intenta resolver cada una de las decisiones tomadas - en qué momento la complejidad pasó a ser más costosa que los beneficios obtenidos - cómo diseñamos y ejecutamos la migración - los retos encontrados durante el proceso - los resultados obtenidos tanto en performance como en gestión - los retos que aún nos quedan pendientes Sin embargo, una parte importante de esta historia no está en los diagramas. También hablaremos del factor humano detrás de la transformación: cómo se construye un equipo capaz de abordar cambios de gran escala, la importancia de la formación continua, la transferencia de conocimiento y la creación de una cultura de colaboración. Aprendimos que la simplificación tecnológica no sucede de un día para otro y que la cohesión del equipo es tan importante como la arquitectura cuando se trata de hacer evolucionar una plataforma crítica Porque al final, las tecnologías cambian pero son los equipos los que permiten que sistemas complejos sigan evolucionando de forma sostenible false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/XY3T7L/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/XY3T7L/feedback/ Rambla Track (Spanish) Open Space 2026-11-14T15:30:00+01:00 15:30 00:30 Open Space 5 devopsdays-barcelona-2026-7151-open-space-5 es Open Space 5 false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/9FCUAQ/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/9FCUAQ/feedback/ Rambla Track (Spanish) Open Space 2026-11-14T16:30:00+01:00 16:30 00:30 Open Space 6 devopsdays-barcelona-2026-7152-open-space-6 es Open Space 6 false https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/SYYKKP/ https://talks.devopsdays.org/devopsdays-barcelona-2026/talk/SYYKKP/feedback/