10 ms·

We are currently using MySQL on RDS for most of our work. We're very tempted to move to Aurora on AWS for the benefits it has around write scaling, disk size sc

by verelo 9y ago

We are currently using MySQL on RDS for most of our work. We're very tempted to move to Aurora on AWS for the benefits it has around write scaling, disk size scaling, table size limits and its claims around improved performance. I assume you're watching these developments, what is your take? Do you plan to compete, mirror or simply go another direction with MySQL?

morgo 9y ago
We compete in the sense that Aurora is a fork of MySQL 5.6 (2013). As a product manager, I do watch Aurora (along with SQL Server, Postgres, MongoDB, MariaDB etc). I'd rather answer questions about our products if you don't mind :-)
- verelo 9y ago
  Fair enough. My biggest question is the same old problem that plagues all databases: Do you have any plans coming up to help us deal with modifying large tables, scaling writes and/or dealing with current known storage limits?
  - morgo 9y ago
    I think plague might be a stronger word than I would use, since I think there is always pressure on new entrants to exaggerate problems with existing technology. For example: I have several customers with 200TB databases on a single server. I helped a customer a few weeks ago insert 50K/queries/s sustained on some not particularly special hardware (higher is possible; depends a lot on schema+indexes). But back to your question - Yes. We are working on improving use cases like insert throughput, and changing the file format so we can support an instant DDL. Having our new data dictionary in 8.0 provides a strong basis for this. The larger vision is a 4 step mission, described in our Keynote from last year: https://www.youtube.com/watch?v=4ihSsQ2z-Cc&feature=youtu.be&t=2707 https://www.youtube.com/watch?v=4ihSsQ2z-Cc&feature=youtu.be... Actual mission slide starts at 57:30. Step 4 is to introduce write scale out with sharding. (Hi btw!, I'm also an Australian living in Toronto.)

by verelo 9y ago

morgo 9y ago

We compete in the sense that Aurora is a fork of MySQL 5.6 (2013). As a product manager, I do watch Aurora (along with SQL Server, Postgres, MongoDB, MariaDB etc). I'd rather answer questions about our products if you don't mind :-)

verelo 9y ago
Fair enough. My biggest question is the same old problem that plagues all databases: Do you have any plans coming up to help us deal with modifying large tables, scaling writes and/or dealing with current known storage limits?
- morgo 9y ago
  I think plague might be a stronger word than I would use, since I think there is always pressure on new entrants to exaggerate problems with existing technology. For example: I have several customers with 200TB databases on a single server. I helped a customer a few weeks ago insert 50K/queries/s sustained on some not particularly special hardware (higher is possible; depends a lot on schema+indexes). But back to your question - Yes. We are working on improving use cases like insert throughput, and changing the file format so we can support an instant DDL. Having our new data dictionary in 8.0 provides a strong basis for this. The larger vision is a 4 step mission, described in our Keynote from last year: https://www.youtube.com/watch?v=4ihSsQ2z-Cc&feature=youtu.be&t=2707 https://www.youtube.com/watch?v=4ihSsQ2z-Cc&feature=youtu.be... Actual mission slide starts at 57:30. Step 4 is to introduce write scale out with sharding. (Hi btw!, I'm also an Australian living in Toronto.)