Why the need for humans won’t disappear in the age of autonomous databases

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

The promise of fully autonomous systems — databases that manage, heal, and optimize themselves amid rapidly increasing data stores — is tantalizing to CTOs. But as Percona co-founder Vadim Tkachenko explained to The New Stack last week, the reality is far more nuanced: While automation is indeed transforming the data landscape, the human element remains not only relevant but essential.

“I think a human still will need to run databases,” Tkachenko told The New Stack. “However, the growth of data is not slowing down. The transformation is not in the disappearance of the (DBA) role, but in its redefinition.”

Percona CTO and co-founder Vadim Tkachenko. Credit: Percona

Speaking during his company’s Percona Live 2026 conference here at the Computer History Museum in Mountain View, California, Tkachenko predicted, “The database administrator of the future will evolve from a mechanic focused on operational upkeep to an architect specializing in the structure of the data itself.”

The Durham, North Carolina-based Percona, which makes popular open-source database software with a set of optional services, celebrated its 20th anniversary at the CHM event. Practical solutions for current workload issues were highlighted over three days of seminars, with experts from AWS, VMware, NEXTGRES, and others contributing their expertise to the discussions.

“The database administrator of the future will evolve from a mechanic focused on operational upkeep to an architect specializing in the structure of the data itself.”

The day-to-day drudgery — the patching, scaling, and maintenance that …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://thenewstack.io/dba-role-kubernetes-autonomous-databases/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.