9 ms·
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
by ksec 5y ago
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 when is 9.0 expected to arrive.
- Thaxll 5y agoYoutube also use MySQL.
- dheera 5y agoWow. Why don't they use in-house Google databases, which are supposedly vastly more scalable than MySQL?
- SQueeeeeL 5y agoProbably because a lot of those benefits don't actually translate that well towards their problem space. These aren't a bunch of 20 year olds throwing together a MongoDB, they're professionals using tools to actually make a product
- williamdclt 5y agoI don't think the people behind Spanner are a bunch of 20yo throwing together a MongoDB
- jacquesm 5y agoBecause there is a substantial cost to such migrations. If it works don't fix it.
- mastersummoner 5y agoWhile "if it ain't broke, don't fix it" is often a perfectly valid approach, there are going to be times when an upgrade can result in significant performance improvements or fewer admin headaches.
- linspace 5y agoDoes anything "just work"? Everything is constantly changing, new features always in demand, more users, more data.
- lazide 5y agoAnd you need to support that for anything you have ON TOP of any migration work - which is huge, and also a similarly moving target
- myohmy 5y agoIf IT is on the value chain this seems insane. If IT is ancillary to the value chain then this is standard.
- vp8989 5y agoYouTube 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?
- WJW 5y agoAs far as I can tell, Vitess still has trouble with cross-server transactions and distributed locking. Presumably something "vastly more scalable" could work around this. The Spanner team noticeably put out https://cloud.google.com/blog/products/databases/inside-cloud-spanner-and-the-cap-theorem https://cloud.google.com/blog/products/databases/inside-clou... a few years back, which tl;drs that they managed to get a reliable enough network that partitions don't really happen anymore and so you can get both C _and_ A from the CAP theorem. I don't think that Vitess is quite at that level, especially since you can self-host it and thus the devs don't have such network-level uptime guarantees.
- vp8989 5y agoAre cross-server transactions scalable? Would anyone architect a system that did them en masse unless they absolutely 100% had to? I am just speculating here but I doubt that YouTube migrated to Spanner so that they could do cross-server transactions. I would think consolidating the Ops burden into the GCP org and also serving as a trophy "customer" were higher on the list of reasons. But again, just speculating...
- derekperkins 5y agoYeah, Google policy was to migrate everything to Spanner, not a technical decision. > Are cross-server transactions scalable? Would anyone architect a system that did them en masse unless they absolutely 100% had to? As a long time Vitess user and contributor/maintainer, this perfectly describes the issue. Minimal effort has been put into solving cross shard / 2PC transactions because a well designed system rarely needs it.
- ksec 5y agoI guess people from PlanetScale will know. Not sure if they are reading the thread.
- gresrun 5y agoYouTube used to use a MySQL-based system called Vitess[0]. It no longer uses it and has migrated to Spanner. [0]: https://vitess.io/ https://vitess.io/
- wikibob 5y agoAh this is interesting. Do you have any references on their migration to Spanner?
- buro9 5y agogresrun works at YouTube, if by reference you mean citation then his comment is it.
- jjnoakes 5y agowikibob was probably looking more for public documentation about the why and how rather than confirmation that the statement is true.
- owaislone 5y agoProbably because Youtube was using MySQL before being acquired and switched to a better, probably fully managed DB that was much easier (free?) to maintain and scale.
- wikibob 5y agoYep, I love watching conference talks or reading Twitter threads, papers, etc about these kind of migrations.
- Thaxll 5y agoThanks for the update! I found more details there: https://opensource.google/projects/vitess https://opensource.google/projects/vitess > How Google uses Vitess > Vitess was serving all YouTube database traffic from 2011 to 2019.
- 5y ago
- deleted 5y ago[deleted]
- dekhn 5y agogoogle internally has always had a split mind about mysql. It never really jibed with the underlying google architecture but played an important role in multiple products (at least partly due to its replication features). Replacing it completely has turned out to be a huge challenge. I gained a fair amount of respect for mysql after seeing it applied at scale, but it was also a bit scary.
- tpetry 5y agoSo 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?
- PeterZaitsev 5y agoNo. MySQL 8 changed its engineering approach with features released in minor releases. In this regard it is like MacOS X or Windows 10, whatever you prefer where features are shipped without major version change
- tpetry 5y agoSure, and this is great. But The newest release is 8.0.26, so there hasn‘t been any minor release yet - in 3 years. And i can‘t find anything about new MySQL features or planned features except the big 8.0 release.
- PeterZaitsev 5y agoThere are new features introduced in 8.0.26 as in .25 .24 etc before that check out release notes.
- fipar 5y agoThere have been several minor releases in the past 3 years: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/ https://dev.mysql.com/doc/relnotes/mysql/8.0/en/
- taywrobel 5y agoIn semantic versioning parlance those would all be considered "patch" releases, not a "minor" release. The minor version segment in a semantic version is the 2nd number, so most people would consider the next "minor release" for MySQL to be 8.1.0. If following the guidance set out at https://semver.org https://semver.org, a patch release wouldn't add any new functionality, it would just address bugs in a backwards compatible way. A minor version would introduce new functionality in a way that doesn't violate backwards compatibility. Quickly scanning the release notes for some of the MySQL 8 versions, they seem to be generally sticking to this; most of the versions fixed some bugs or unintuitive behavior, but it doesn't look like much new functionality has been introduced since 8.0.4, the last release candidate for the major version bump.
- MuffinFlavored 5y ago> At the scale of Facebook I wonder if they are the largest MySQL user on the planet I have to imagine they use other databases as well, right? We're much smaller than Facebook and we have some Mongo and some Postgres and a mix of Go/Rust/Scala/node.js. I wonder how many boxes they have dedicated to be being MySQL machines. I wonder how big their tables are and how many writes per second they see during the day.
- hodgesrm 5y agoTheir scale is enormous. I first heard the phrase "thundering herds" in a Facebook MySQL talk. (Thundering herds refers to what happens to your infra when something big happens in real life that lights up social networking/search/etc.)
- MuffinFlavored 5y agoLet's try to put a guess in numbers. > With roughly 2.85 billion monthly active users as of the first quarter of 2021 > 1.8 billion of Facebook users (66%) use the app on a daily basis Say 1 database could store the data + handle the reads/writes for 100,000 users (literally just guessing) 2.85 billion monthly active users / 100k users per server = 28,500 servers/"instances" for MySQL That's not even counting Kubernetes pods (if they use that) running Docker containers (if they use that) for their API / content serving. I wonder what their average transactions per second looks like. For Twitter: > Every second, on average, around 6,000 tweets are tweeted on Twitter, which corresponds to over 350,000 tweets sent per minute, 500 million tweets per day and around 200 billion tweets per year. > As of the first quarter of 2019, Twitter averaged 330 million monthly active users Twitter has 11.5% the MAU of Facebook (330m of 2.85b)? I don't know if 1 tweet can be extrapolated to 1 Facebook like/comment/share/post but if it did, 6k tweets per sec * 8.7x the user base = 52.2k writes per second? Found this: > Facebook now has about 30,000 servers supporting its operations, hosts 80 billion photos, and serves up more than 600,000 photos to its users every second.
- packetslave 5y agoKubernetes, no. Twine (aka "Don't call it Tupperware"), yes https://engineering.fb.com/2019/06/06/data-center-engineering/twine/ https://engineering.fb.com/2019/06/06/data-center-engineerin... Also, that "30,000 servers" number is off by... a lot. No comment on by how many orders of magnitude. :-)
- fowl2 5y agoGitHub also seems to use MySql, as recently as 2020[1] [1] https://github.blog/2020-05-20-three-bugs-in-the-go-mysql-driver/ https://github.blog/2020-05-20-three-bugs-in-the-go-mysql-dr...
- derekperkins 5y agoStill do
- merlinscholz 5y agoThe NSA also uses MySQL for their project XKEYSTORE (digital surveillance)
- daniel_iversen 5y agoWe used MySQL at Dropbox too, and they probably still do.
- pbreit 5y agoAny idea what Facebooks stores in MySQL? Core user database?
- kevinventullo 5y agoTo a first approximation, everything. Most product engineers interact with it by querying TAO, which you can read about in various blog posts, but is basically a cache in front of MySQL (this is a vast oversimplification).
- notacoward 5y agoHi, Kevin. :) As of the time I left, the bulk storage system I worked on - images, video, machine-learning datasets, backups of other things, etc. - held most of the bytes at Facebook. The MySQL/TAO complex had orders of magnitude more addressable objects, undoubtedly handled many times more requests and bytes in flight per second, but when it comes to bytes at rest they're not even number one.
- kevinventullo 5y agoFair enough :)
- notacoward 5y agoBasically all the small stuff. Every user's identity, preferences, history, and connections. If you post text, that's there too. If you post media, that's somewhere else. Connections are the hard part, because it's a gigantic graph with the potential to make every query - e.g. to construct a user's timeline - hit vast numbers of servers. There's all sorts of special sauce to do with partitioning, caching, etc. to absorb as much as possible of that load before it hits the MySQL servers, but it's still a gigantic service even by Facebook standards.