[0]: https://www.percona.com/doc/percona-server/5.7/index.html
Knowing what to be careful with on MySQL, I would certainly consider using the Percona flavor again in a new application.
Table had a field that was varchar(128) and wasn't used (original filename but system generated a hashed filename and served it with that name (for sharding, lots of files)) so for 5 years MySQL had been silently killing everything > 128 characters and it didn't matter.
Then along comes our hero (me in this story) who does all the upgrades, tests everything thoroughly (he thought) and it's all fine, deploy, test everything fine.
Next morning, 9 bug reports "Can't upload files at all FIXITNOW!!!".
Turns out company was auto generating PDF's from some report software that dumped all the data into the filename and none of them where less than 128 chars.
MySQL 5.7 started not silently dumping data into the bitbucket in the sky and instead threw an error (when quite reasonably you tried to shove 300 characters into a varchar(128)).
TLDR: MySQL doing the right thing broke the broken.