<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spanish on Percona Community</title><link>https://percona.community/talk_tags/spanish/</link><description>Recent content in Spanish on Percona Community</description><generator>Hugo</generator><language>en-us</language><copyright>© Percona Community. MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.</copyright><atom:link href="https://percona.community/talk_tags/spanish/index.xml" rel="self" type="application/rss+xml"/><item><title>What Databases Reveal About the True Cost of Kubernetes</title><link>https://percona.community/talks/2026/2026-11-18-what-databases-reveal-about-the-true-cost-of-kubernetes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://percona.community/talks/2026/2026-11-18-what-databases-reveal-about-the-true-cost-of-kubernetes/</guid><description>&lt;p>Databases are among the most demanding workloads running on Kubernetes. They stress storage, observability, backup, and recovery systems in ways that many stateless applications never do.Drawing on years of production troubleshooting and performance investigations across PostgreSQL and MySQL environments, this talk examines what databases reveal about the operational realities of Kubernetes.We&amp;rsquo;ll discuss common failure patterns, the strengths and limitations of database operators, performance expectations versus production behavior, and why many database incidents originate in the surrounding platform rather than the database itself.This is not a talk about whether databases belong on Kubernetes. Instead, it is a practical look at the tradeoffs, complexity, and operational costs that emerge when stateful systems meet cloud-native infrastructure.Attendees will leave with a framework for evaluating database platform decisions based on reliability, performance, and operational cost.&lt;/p></description></item></channel></rss>