News for hackers. Stuff that matters.

A comment on Design Considerations for High-Throughput Cloud-Native RDBMS [pdf]. Parent comment

Re:Design Considerations for High-Throughput Cloud-Native RD... by sciurus on Wednesday January 16, 2019 @08:44AM (#18920720)
What flavor of Aurora were you using, and which RDS engine and version did you switch to?

Within Amazon's Aurora and RDS product families (https://aws.amazon.com/rds/), there are

* Amazon Aurora MySQL

* Amazon Aurora PostgeSQL

* Amazon Aurora Serverless

* Amazon RDS for MySQL

* Amazon RDS for MariaDB

* Amazon RDS for Oracle

* Amazon RDS for SQL Server

plus the variations in different versions (e.g. Amazon RDS for MySQL supports 5.5, 5.6, 5.7, and 8.0).

Without knowing that it's hard to understand how you solved your problem. E.G. If you switced from Aurora MySQL to RDS for MySQL i expect you'd still need to use a tool like pt-osc and copy your tables.

[ Parent | on HN ]
Re:Design Considerations for High-Throughput Cloud-Native RD... by stevev on Wednesday January 16, 2019 @11:09PM (#18928309)
We were on Aurora MySQL with the highest tier available. Switched to RDS MySQL 5.7. AWS has a database migration tool that we used to migrate over.
[ Parent | on HN ]
Re:Design Considerations for High-Throughput Cloud-Native RD... by hnmonkey on Thursday January 17, 2019 @06:21PM (#18935616)
Hey stevev I know it's been a bit since you made this comment but could you provide further details on the tool and the benefits you found from the switch? I'm currently on Aurora MySQL and have hundreds of GB and am feeling it in a not great way. I'd love to get a feel for a path forward that could be better.

Thanks!

[ Parent | on HN ]