Netflix Billing Migration to AWS
21–30 of 126 posts
Re: Netflix Billing Migration to AWS
#22Dropped Oracle, using MySQL. Why not use PostgreSQL instead?
A large company describes their very real efforts and shares their experience and knowledge, and the first comment is "Why not use instead?".
Re: Netflix Billing Migration to AWS
#23How many times is Netflix going to finalize its transition to AWS?
Re: Netflix Billing Migration to AWS
#24Dropped Oracle, using MySQL. Why not use PostgreSQL instead?
Re: Netflix Billing Migration to AWS
#25Dropped Oracle, using MySQL. Why not use PostgreSQL instead?
Is there a version of poe's law for hacker news / slashdot? A large company describes their very real efforts and shares their experience and knowledge, and the first comment is "Why not use instead?".
Postgres is usually the first choice for applications like this so knowing why they chose something else over that could influence others that need to make a similar decision.
Re: Netflix Billing Migration to AWS
#26How many times is Netflix going to finalize its transition to AWS?
Re: Netflix Billing Migration to AWS
#27They used a DRBD replicated MySQL. Wonder why they used MySQL over PostgresSQL then.. Would be great to know if they looked that up aswell.
https://aws.amazon.com/blogs/aws/cross-region-read-replicas-...
https://aws.amazon.com/about-aws/whats-new/2016/06/amazon-rd...
I am interested in non-read replica replication...
Re: Netflix Billing Migration to AWS
#28I got really excited because I read the heading as Netflix migration costs paid for by AWS. I thought they worked out deal to get a free tier during migration. Wow...oh...nevermind... :-)
Re: Netflix Billing Migration to AWS
#29Dropped Oracle, using MySQL. Why not use PostgreSQL instead?