Live data from Hacker News

Migrating Facebook to MySQL 8.0

engineering.fb.com

81–90 of 336 posts

Re: Migrating Facebook to MySQL 8.0

#81

Earlier quoted context omitted.

Don't forget IBM

What's it like working at IBM? I've seen it get good ratings online

This question is extremely hard to answer, because IBM has ~345k employees in 177 counties. It's anywhere from 0/10 to 10/10.

Re: Migrating Facebook to MySQL 8.0

#82

My old-man brain still can't compute this statement: "MySQL, an open source database developed by Oracle" . I know this is now factually true, but late-90s me keeps looking over my shoulder and freaking out.

I think MySQL Engineering team does great job with Engineering, Do not want to deal with Oracle Sales ? I would invite you to talk to Percona for Commercial Support and Services Options

Full disclosure - I'm CEO at Percona :)

Re: Migrating Facebook to MySQL 8.0

#83
post #70
post #56

Earlier quoted context omitted.

YouTube built Vitess, which lets you scale out MySQL writers. If I can scale out both my writers and my readers then what could be "vastly more scalable" than that?

Spanner paper: https://static.googleusercontent.com/media/research.google.c... It is designed from the ground-up to be globally distributed. Some other databases like FoundationDB (now owned and killed? by Apple) and CockroachDB were designed to scale across multiple datacenters. Correction: FoundationDB is alive as open-source again, yay!

FoundationDB was re-released as open source a couple of years ago.

https://www.foundationdb.org/

Re: Migrating Facebook to MySQL 8.0

#84
post #60
post #57

Earlier quoted context omitted.

YouTube used to use a MySQL-based system called Vitess[0]. It no longer uses it and has migrated to Spanner. [0]: https://vitess.io/

Ah this is interesting. Do you have any references on their migration to Spanner?

gresrun works at YouTube, if by reference you mean citation then his comment is it.

Re: Migrating Facebook to MySQL 8.0

#85

Earlier quoted context omitted.

I find the comments in this article very accurate: https://news.ycombinator.com/item?id=15160149 > ORA is the elephant's graveyard of software. > Once something gets bought by them, you know it is done. Slowly, but surely. > They perform a function akin to the maggots that destroy cadavers in nature. Part of the overall ecosystem. > ORA stopped being a tech co a while ago, now it is a finance play. Use cash to buy a…

And yet MySQL is very much alive..? Java has fully opensource implementations too, and has had innovations like GraalVM and Jakarta EE. I think I'm too young to hate Oracle with a burning passion. I would be very scared of their sales/corporate team, but I mean, even having large contracts with Google or Amazon is difficult to say the least.

MySQL is alive for companies already using MySQL, but would well informed companies be choosing it today? I'm not so sure.

I think you either want it to have more functionality and you choose Postgres, you want a particular performance profile and you pick MariaDB, or you want the enterprise support and you pick Oracle's database. Why you would pick Oracle-supported MySQL today I'm not sure.

Re: Migrating Facebook to MySQL 8.0

#86

I wonder what order of magnitude of rows they deal with and how they optimize indices for querying that data.

Like everyone else?

I didn't downvote you, but you were downvoted for this. So maybe I'll explain further, instead, to stir conversation.

As you deal with more and more rows, it becomes imperative that all of your where clauses hit indexes/indices, but even beyond that, with large enough row sizes, it's not enough to provide fast responses.

I suspect they deal with this in the form of some sort of caching outside of MySQL, but I haven't read into it.

I'd be curious about how you respond to such challenges at the billions or trillions of rows orders of magnitude. Millions can be difficult enough, but beyond that you may have queries that effectively never return if you do not plan.

Related reading:

[1]: https://dba.stackexchange.com/questions/20335/can-mysql-reas...

[2]: http://webscalesql.org

Re: Migrating Facebook to MySQL 8.0

#87
post #6

MySQL 5.6 was released on 5 February 2013 . MySQL 8.0 was released on 19 April 2018 . >The 8.0 migration has taken a few years so far. We have converted many of our InnoDB replica sets to running entirely on 8.0. At the scale of Facebook I wonder if they are the largest MySQL user on the planet. And I take this opportunity to ask, does anyone know how does the MySQL roadmap works? What sort of features are coming or…

So there has not been any major improvement in MySQL for 3 years? There hasn‘t been released any minor version? Can someone explain the current state more?

Re: Migrating Facebook to MySQL 8.0

#90
post #70
post #56

Earlier quoted context omitted.

YouTube built Vitess, which lets you scale out MySQL writers. If I can scale out both my writers and my readers then what could be "vastly more scalable" than that?

Spanner paper: https://static.googleusercontent.com/media/research.google.c... It is designed from the ground-up to be globally distributed. Some other databases like FoundationDB (now owned and killed? by Apple) and CockroachDB were designed to scale across multiple datacenters. Correction: FoundationDB is alive as open-source again, yay!

AFAIK, FoundationDB is alive and well. What makes you think it's killed?
Post reply on HN