Well 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.
RonDB 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.
