Migrating Facebook to MySQL 8.0

Post by fipar » Thu, Jul 22, 2021, 7:34 PM UTC

tpetry wrote: post #111

PeterZaitsev wrote: post #106

Earlier quoted context omitted.

No. 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

Sure, 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.

Post by twic » Thu, Jul 22, 2021, 7:34 PM UTC

munk-a wrote: post #96

lucideer wrote: post #74

Earlier quoted context omitted.

That was the expectation but the Oracle camp surprised everyone by actually giving it some attention, and meanwhile MariaDB's promise of being a "100% compatible drop-in replacement" came with more and more caveats with each release (as is to be entirely expected with any fork). When you consider the network effect of all the stacks already heavily invested in MySQL, all Oracle really needed to do was put in a modicu…

I carried out a (quite ill-advised in retrospect) migration from MySQL to Postgres on a mature codebase with absolutely no automated test coverage and it went pretty smoothly. We had some bumpy performance directly after the production migration but we were able to reach parity after about two months of observing and adding targeted indices. I absolutely adore Postgres's tweaks to the SQL language, that dialect is am…

Post by PeterZaitsev » Thu, Jul 22, 2021, 7:36 PM UTC

hellcow wrote: post #117

sltkr wrote: post #108

Earlier quoted context omitted.

I was curious so I looked up the differences here: https://mariadb.com/kb/en/mariadb-vs-mysql-compatibility/ It doesn't sound too bad. The incompabilities seem to be mostly stuff like not being able to generally use replication from MySQL to MariaDB or vice versa. But I would guess that's not a very common case anyway: most users are either developers that want their software to work with both MariaDB and MySQL (whic…

The issues I encountered while using MariaDB in place of MySQL were subtle -- most things worked as expected, which makes the issues so much more unexpected. But at the end of the day, the same migrations produced a different schema. Arguably MariaDB made the correct decision to fix some MySQL 5.7 bugs that we were unwittingly relying upon, but the different behavior caused issues for us all the same. Rather than wor…

Post by freedomben » Thu, Jul 22, 2021, 7:43 PM UTC

lucideer wrote: post #74

takeda wrote: post #61

Perhaps it's due to me being in the PostgreSQL camp, but what happened to MariaDB? I was convinced that's where MySQL developers went and that's where development proceeded, while MySQL was just half dead, because Oracle did not care about it.

That was the expectation but the Oracle camp surprised everyone by actually giving it some attention, and meanwhile MariaDB's promise of being a "100% compatible drop-in replacement" came with more and more caveats with each release (as is to be entirely expected with any fork). When you consider the network effect of all the stacks already heavily invested in MySQL, all Oracle really needed to do was put in a modicu…

Post by ksec » Thu, Jul 22, 2021, 7:48 PM UTC

WJW wrote: post #67

vp8989 wrote: 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?

As 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-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…