5 ms·
I work on the Netflix Billing Team. PostgreSQL was indeed a very attractive option, but we wanted to keep a path to Aurora open. When we were working on the mi
by lapitopi 10y ago
I work on the Netflix Billing Team.
PostgreSQL was indeed a very attractive option, but we wanted to keep a path to Aurora open. When we were working on the migration, Aurora was still in beta, so instead of going to Aurora directly, we decided run our own MySQL instances on EC2.
- lilbobbytables 10y agoAhhh, now it makes sense. Thanks for answering.
- philliphaydon 10y agoWhy would you go to RDS with such large amounts of data when AWS do not provide ability to get data out easily. If you moved away from AWS in the future for what ever reason your data is more or less stuck in AWS.
- jon-wood 10y agoAmazon released their data migration service a while back, which allows you to transfer data in just about anyway you might want to, they'll migrate data between different RDS engines (MySQL to Postgres for example), and to databases outside AWS. They even support near real-time replication to database servers outside AWS, so you could hypothetically replicate your RDS instances to a fail over environment with another provider. There's very little risk of your data being locked in now. [1] https://aws.amazon.com/dms/?nc2=h_mo https://aws.amazon.com/dms/?nc2=h_mo
- philliphaydon 10y agoUnless you use SQL Server. The dms service is basically useless with sqlserver. We can't get our 200gb do out of AWS. And any method that works without dms takes about 40 hours.
- toomuchtodo 10y agoCan you replicate to a slave outside of RDS and then perform a replica promotion during scheduled maintenance?
- Annatar 10y agoDoes "Aurora" fix the inherently broken SQL and integrity constraint mishandling associated with MySQL? Which security models does "Aurora" offer, for instance, are you able to use OS authentication like in Oracle? What about PKI on SmartCards?