Even the developers who were resistant due to the different data model have completely embraced it.
One of MySQL's greatest strengths is the maturity of its ecosystem. Tons of existing automation, a relatively large number of skilled developers you can hire, multiple dedicated conferences, good free online docs, dozens of books, several top-notch consulting firms for handling the crazy edge cases.
I'll readily admit that MySQL has its flaws, but personally I wouldn't rank difficulty of maintenance operations high on the list... at least from a practical perspective, and relative to other comparable data stores used at a massive scale.
In my experience, no matter what databases you choose, if you "go big" you can't ever escape the need for robust automation and a decent amount of in-house talent.
But cluster elasticity and resiliency has been working really good so far.
Thanks.
Sure, it's got some cool big data stuff, but try doing any of those "maintenance" operations on other databases without ripping your hair out. For example, even bringing up a new MySQL slave is a huge pain in the ass, let alone doing something non-trivial like promoting a new master.