@jfg956 I'd agree but we come from similar backgrounds. The important thing is you have (i) enough redundancy to handle the hardware "failure" and also have good automatic failover to reduce the outage time on applications while they reconfigure to talk to a replacement. A tradeoff.
@Percona@TheRegister 8.0 to 8.4 is way easier for users, but if you manage replication yourself and use the older master/slave technology then you need to update to use the newer source/replica updated equivalents. That may lead to quite a bit of work if you're not prepared.
I am on the #FOSDEM#MySQL DevRoom Committee, you have until December 1st (2024) to send you talk submission. And by submitting there, you might also have the chance to talk at the fringe event Pre-FOSDEM MySQL Belgian Days !
https://t.co/Lr3CKV2Mgs
Interesting post from Peter: How Can MySQL Catch Up with PostgreSQL’s Momentum? https://t.co/wDdkTfI97E. Adding more hooks via the component infrastructure into MySQL might be a great way to make it more extensible.
MMUG25: Cómo https://t.co/Kia6UPY8QL usa MySQL / Operador de Kubernetes para MySQL https://t.co/uiF8GycqLM #Meetup via @Meetup
Come and see us on Monday.
This was a disappointment. It's good to bring up the concern: In Search of Transparency at FOSDEM https://t.co/ikIBDD5uyi. Hoping to take part in 2025.
An interesting day This is me talking yesterday in a fireside chat at the Percona Open Source Database Conference in Madrid with @peppla and others. @mysql@Percona@mariadb
@morgo Morgan, MySQL 8.1 is out and 8.2 is expected very shortly. Usage of 8.1+ may not be high yet, but unless something significant changes I'd expect spirit to work on these versions too.