3 ms·
RonDB is the 3rd fork of MySQL (after PerconaDB and MariaDB). However, it is a fork of MySQL Cluster (NDB cluster database engine), not InnoDB. And this time, i
by jamesblonde 5y ago
RonDB is the 3rd fork of MySQL (after PerconaDB and MariaDB). However, it is a fork of MySQL Cluster (NDB cluster database engine), not InnoDB. And this time, it's the inventor of the storage engine that is doing the forking. Mikael Ronstrom invented NDB Cluster, a distributed in-memory database, when he was a Ericsson in the late '90s and MySQL bought it off Ericsson in 2003 (or 2002?). Now, Mikael is working on a cloud-native distribution of NDB, RonDB, at Logical Clocks. NDB always had a reputation as high throughput, low latency, and difficult to configure/operate. RonDB is about fixing those flaws as a cloud native service.
- ransom1538 5y agoWell I hope this time when they work on MySQL Cluster they add auto-sharding tables so we can increase writes. Because if they don't, I don't see the point. Sure, when I had to go to a colocation and plug in wires having an auto repairing MySQL Cluster made tons of sense. Now? I can spin up a large disk db machine in 4 minutes flat. We need a way to split db writes across VMs now. GCP and AWS just gave up on this problem. Hell, GCP doesn't even have a reader endpoint. But money is just sitting there for someone to invent.
- mikaelronstrom 5y agoRonDB has the capabilities to both scale on VM size and number of VMs as online operations. The auto part requires that we support in the managed version as well. Hopsworks have added auto-scaling to AI worker nodes. So auto-scaling in RonDB seems like a natural progression to this. Thx for the suggestion.