The Next Decade in Data Management
summary
Argues that MySQL won by being good enough for early web scale but modern web apps demand scale-out designs that assume hardware failure, absorb “fire hose” telemetry, and favor single-record put/get and well-designed APIs over traditional query languages; cites Berkeley DB, Hadoop and columnar systems (Vertica) as practical tools; predicts years of Darwinian experimentation then consolidation under a rule of three market, and critiques eventual consistency is a sop while advocating for stronger distributed consistency and analytics at thousands-node scale.
AI-written summary · about
chapters (4)
related talks
28mRelational Databases Don't call it a comeback!
27mDistributed MySQL Architectures: Past, Present and Future
50mA Short Summary of the Last Decades of Data Management
30mThe database trends that are transforming your database infrastructure forever
51mDatabase systems: a decade of disruption and innovation
55mThe Future of MySQL
55mThe Great Data Debate 2022
56mWelcome & State of Open Source Databases