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

How to change MySQL account passwords with no downtime

Changing the password of a MySQL account that an application uses was hard before MySQL 8.0. It is easy in MySQL 8.0 and later, thanks to two clauses of ALTER USER: RETAIN CURRENT PASSWORD and DISCARD OLD PASSWORD.

Read more

Six connections and a long queue: how a TLS-inspecting proxy quietly turned HTTP/2 into HTTP/1.1

I recently tracked down a performance problem that turned out not to be in the application, the servers, or the CDN. A corporate TLS-inspecting proxy sat between the users and the site.

Read more

How easy is it to use the VillageSQL MCP extension?

VillageSQL published Access MySQL over MCP with vsql-mcp . The extension serves the Model Context Protocol from inside the database, so an agent talks to MySQL over Streamable HTTP without a sidecar holding a credential.

Read more