Leveraging Open Source Databases for Strategic Advantage
summary
Concrete takeaways and outcomes not buzzwords: practical migration notes, two repeated case studies, exact numbers and where things broke. An airline moves a small Oracle workload into Hadoop then into PostgreSQL and ends up saving 100 GB workload and about 70k per year after the fixes; migrations cost time and political capital. MongoDB relicensing (the SSP license 2018 change) creates vendor lock and spawns incompatible cloud alternatives. Tools named: PostgreSQL, MySQL, SQLite, MongoDB, Hadoop, Percona, Cloudera — and the claim is open standards plus open source preserve portability.
AI-written summary · about
chapters (9)
- 0:00Strategic database choices
- 5:30Why database choice matters
- 12:43Database popularity trends
- 15:32Failed Oracle migration case
- 22:55Open source advantages
- 29:43Open standards vs vendor lock-in
- 31:07MongoDB license controversy
- 39:53Future of MongoDB alternatives
- 40:35Q&A
related talks
38mOpen Source - A Blessing or a Curse?
25mState of Open Source Databases
48mMigrating to PostgreSQL: Strategies, Sovereignty, and Success
46mThe Top 10 Mistakes When Migrating Oracle Databases to PostgreSQL
30mThe database trends that are transforming your database infrastructure forever
56mWelcome & State of Open Source Databases
36mTales from the Postgres Front, and What We Can Learn
21mDriving the Future of PostgreSQL Adoption
