[leedo__]

Last I investigated Galera it lacked support for query caching. Over 50% of our queries are cache hits, so it made it hard to justify using Galera over a normal master+slave setup. However I could see it being useful for setups where a single server can't handle the load (we average 300 queries/sec on a single server with lots of room to spare.)

[nknighthb]

They still disable the query cache, but MySQL's query cache generally isn't considered all that great a thing anyway, so few people care. You're better off making judicious use of Redis or memcached.

The biggest win for Galera is high-availability that actually works with minimal effort. (I've never experienced a high-availability solution not based on multi-master/all-nodes-hot principles that didn't cause more problems than it solved.)

They also claim some scalability wins at the front end, but I haven't really tested that, and am content with the performance not being terrible.

[blantonl]

but MySQL's query cache generally isn't considered all that great a thing anyway

You've never had to prime a query cache on a MySQL server, have you? :)

[nknighthb]

Of course not. I use a caching layer with lower overhead that doesn't invalidate the entire cache when a single record changes. The query cache just isn't competitive.