3 ms·

https://github.blog/2018-06-20-mysql-high-availability-at-github/ https://github.blog/2018-06-20-mysql-high-availability-at-gi... depends what you mean by mass

https://github.blog/2018-06-20-mysql-high-availability-at-github/ https://github.blog/2018-06-20-mysql-high-availability-at-gi... depends what you mean by massive scale, but mysql can certainly handle a website of say, stackoverflows size, on beefy hardware with read replicas. facebook would be another story entirely

nindalf 4y ago
Facebook uses MySQL. All the data is one MySQL table.
- dalyons 4y ago
  But not one physical table. It is certainly sharded across 1000s of machines. Basically a tuple store at that point, rather than a rdbms
- evanelias 4y ago
  > All the data is one MySQL table This is not correct at all. Facebook has many distinct MySQL tiers (distinct sets of shards) supporting different purposes. And each tier has many tables. The UDB tier (user database / primary product backing store) had several hundred tables when I worked on Facebook's MySQL team 7+ years ago. This was before the MyRocks migration though, and it's possible the UDB layout changed to reflect MyRocks' extensively different file layout vs InnoDB. But in any case, especially keeping in mind all the various distinct tiers, saying all data at Facebook is one table is egregiously incorrect.