3 ms·
"We wanted a system that is masterless (or all-master) in the sense that any node can fail at any time and the system doesn't care." Neither PostgreSQL, nor My
by zzzcpan 10y ago
"We wanted a system that is masterless (or all-master) in the sense that any node can fail at any time and the system doesn't care."
Neither PostgreSQL, nor MySQL can do much here and this is actually why we have the nosql movement. These problems are fundamentally unsolvable with the trade offs those RDBMSs made.
- erichocean 10y agoahem CockroachDB would like a word…
- zzzcpan 10y agoThey came out of the same movement, you can be pretty sure they didn't take the same trade offs.
- kodablah 10y agoAnd that's why we have the "NewSQL" movement, though a bit slow. The benefit of NoSQL in some cases (Cassandra and HBase for me) is that it restricts developers from using non-scalable data structuring and querying. RDBMS's have a bad reputation primarily because how they were used via unrestricted queries that came back to haunt the product owners. And even then, some local DB approaches are fundamentally unsolvable in a distributed way (CAP, exactly-once-sends, etc) without trading something, even with cockroach.
- thom30 10y agoMySQL actually just officially released "Group Replication" a few months ago to address this. http://mysqlhighavailability.com/gr/doc/ http://mysqlhighavailability.com/gr/doc/ > MySQL Group Replication is a MySQL Server plugin that provides distributed state machine replication with strong coordination between servers. Servers coordinate themselves automatically, when they are part of the same replication group.