Lessons from two decades of hacking the proprietary value into open so
summary
Twenty years of vendor work yields concrete moves: Percona ships Postgres distributions, PGMonitor, backups and PGTDE (Transparent Data Encryption) to meet PCI/enterprise needs; when Postgres lacked an OIDC validation library Percona implemented it, got a bug report and a patch and already has enterprise pilots; a bank required Kerberos support for a monitoring agent because changing auth would take four years; fragmentation (tens–hundreds of extensions), Kubernetes’ 14‑month realistic lifecycle, and MySQL 5.7 EOL 2023 are recurring practical blockers.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker background
- 3:15About Percona and its open source focus
- 7:12Proprietary value in open source databases
- 10:00Lesson one: Feature weight and enterprise needs
- 13:57Lesson two: Fragmentation challenges
- 18:59Lesson three: Enterprise contributions to open source
- 23:36Lesson four: Drawing inspiration from proprietary solutions
- 26:46Lesson five: Adoption pace and feedback loops
- 29:16Lesson six: Little gaps and non-negotiable features
- 34:13Lesson seven: Integration and certification hurdles
- 37:48Lesson eight: End of life support challenges
- 41:41Summary and closing remarks
- 42:45Q&A: Hardening and trust in open source
- 46:19Q&A: Encryption compliance in regulated environments
related talks
23mFuture Postgres Challenges
12mContribution Over Control Open Source Responsibility in PostgreSQL
19mPostgreSQL Challenges
38mOpen Source - A Blessing or a Curse?
21mDriving the Future of PostgreSQL Adoption
17mPostgres Over the Horizon...
18mPower Hour, Managing Databases at Scale – Peter Zaitsev
47mThe Next 20 Years