News for hackers. Stuff that matters.

A comment on Netflix Billing Migration to AWS. Parent comment

Re:Netflix Billing Migration to AWS by philliphaydon on Wednesday June 22, 2016 @01:26AM (#11951742)
Why 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.
[ Parent | on HN ]
Re:Netflix Billing Migration to AWS by jon-wood on Wednesday June 22, 2016 @03:07AM (#11952057)
Amazon 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

[ Parent | on HN ]
Re:Netflix Billing Migration to AWS by philliphaydon on Wednesday June 22, 2016 @06:25AM (#11952684)
Unless 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.
[ Parent | on HN ]
Re:Netflix Billing Migration to AWS by toomuchtodo on Wednesday June 22, 2016 @01:56PM (#11955727)
Can you replicate to a slave outside of RDS and then perform a replica promotion during scheduled maintenance?
[ Parent | on HN ]