Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Netflix Billing Migration to AWS

techblog.netflix.com

Post reply on HN
Print view View original

11–20 of 126 posts

Re: Netflix Billing Migration to AWS

#11

Post by beachstartup »

merb wrote: post #9
gdulli wrote: post #8

Earlier quoted context omitted.

I think it's just a reflex for (ex-MySQL) Postgres users to ask that anytime they see someone using MySQL. If you have significant experience with both you know the quality of life is different between the two.

Actually I never used MySQL really. But sometimes it's great to know why decisions are made. Actually I don't think they said, "well lets use MySQL over Oracle" especially since MySQL is a Oracle product, too. There would've been a way to use MariaDB aswell. And I guess anything with license costs fall out already (they explained why in the article). Edit: My guess would be that they still keep galera in mind, but si…

it's probably because they still had oracle software and support contracts in place, and in-house knowledge of mysql.

Re: Netflix Billing Migration to AWS

#13

Post by emcrazyone »

crisopolis wrote: post #5

At least they ditched Oracle (licensed)...

I worked at a Fortune-5 that was heavily invested in Oracle.

Oracle has a nasty licensing model where they charge you per core regardless of if that core is a physical one or not (hyper-threading). While I was there, it suites told all the engineering managers that Oracle was out and the going forward solution was Microsoft SQL which, as I understand, has more relaxed licensing model.

Another thing I'm wondering about is I would figure Netflix to be big enough to have SAN storage. Just about every large company I worked at always used SAN replication technologies instead of open source stuff. And it's not a debate about open source solution vs. commercial. It's more about support. Large companies want a throat to grab when things break bad.

Re: Netflix Billing Migration to AWS

#14

Post by matt_wulfeck »

emcrazyone wrote: post #13
crisopolis wrote: post #5

At least they ditched Oracle (licensed)...

I worked at a Fortune-5 that was heavily invested in Oracle. Oracle has a nasty licensing model where they charge you per core regardless of if that core is a physical one or not (hyper-threading). While I was there, it suites told all the engineering managers that Oracle was out and the going forward solution was Microsoft SQL which, as I understand, has more relaxed licensing model. Another thing I'm wondering abou…

Netflix doesn't have SAN because it doesn't run anything outside of AWS. AWS provides the throat to hold in your analogy.

Re: Netflix Billing Migration to AWS

#17

Post by c17r »

emcrazyone wrote: post #13
crisopolis wrote: post #5

At least they ditched Oracle (licensed)...

I worked at a Fortune-5 that was heavily invested in Oracle. Oracle has a nasty licensing model where they charge you per core regardless of if that core is a physical one or not (hyper-threading). While I was there, it suites told all the engineering managers that Oracle was out and the going forward solution was Microsoft SQL which, as I understand, has more relaxed licensing model. Another thing I'm wondering abou…

MS SQL used to be per socket pricing. With 2012 they switched to per core.

That was a sad day.

Re: Netflix Billing Migration to AWS

#18

Post by ww520 »

DRBD works very well for high availability, especially good to provide failover for master database, since that usually requires fast failover like under 10 seconds. Five or six years ago, did couple HA setup with DRBD along with Linux HA and virtual IP. The failover work great.
Post reply on HN