MySQL Roadmap

Here are some notes from the MySQL Server Roadmap session at the MySQL Conference 2007.

MySQL: Past and Future

  • 2001: 3:23
  • 2003: 4.0 UNION query Cache Embedded
  • 2004: 41. Subqueries
  • 2005: 5.0 Stored Procedures, Triggers, Views
  • Now: 5.1.17 Partitioning, Events, Row-based replication
  • 2007?: 6.0 Falcon, Performance, Conflict detection
  • 2008?: 6.1 Online Backup, FK Constraints

2007 Timeline

  • Q1: 5.1 Beta, 5.1 Telco Production Ready, Monitoring Service 1.1, MySQL 6.0 Alpha, Community GA
  • Q2: MySQL 6.0 Beta, New Connectors GA
  • Q3: 5.1 RC, 6.0 Beta, MS 2.0, Enterprise Dashboard beta
  • Q4: 5.1 GA, 6.0 Beta

Where are we today?

  • We are by fare the most populate open source database
  • The Enterprise world is moving online and MySQL is well-positioned for that trend, But:
    • Transactional scalability
    • Manageability
    • Specific online features

MySQL Server Vision – The Future

  • Always Online — 24×7, Online backup,online analytics, online schema changes
  • Dynamic Scale-out — online partitioning, add node, replication aides,
  • Reliable — fault-tolerant, easy disagnosis, stable memory, ultimately self-healing
  • High-performance — Interactive web, real-time response, apps, 10,000-100,000 clients
  • Ease of use — Portable, Best for development, multiple connectors, easy tuning
  • Modularity and Ubiquity — Storage engines, plug ins

How can you help?

  • Bug finding and fixing — Community Quality Contributor
  • Feature/patch contribution
  • But, to expedite your patch

The goal: “Be the Best Online Database for Modern Applications”

Tagged with: Databases General MySQL MySQL Conference &Amp; Expo 2007

Related Posts

More CPUs or Newer CPUs

In a CPU-bound database workload, regardless of price, would you scale-up or scale-new? What if price was the driving factor, would you scale-up or scale-new? I am using as a baseline the first available AWS Graviton2 processor for RDS (r6g).

Read more

An Interesting Artifact with AWS RDS Aurora Storage

As part of using public datasets with my own Benchmarking Suite I wanted upsize a dataset for larger volume testing. I have always used the INFORMATION_SCHEMA.TABLES data_length and index_length columns as a sufficiently accurate measurement for actual disk space used.

Read more

How long does it take the ReadySet cache to warm up?

During my setup of benchmarking I run a quick test-sysbench script to ensure my configuration is right before running an hour+ duration test. When pointing to a Readyset cache where I have cached the 5 queries used in the sysbench test, but I have not run any execution of the SQL, throughput went up 10x in 5 seconds.

Read more