We don't have any auto scaling for either up or down scaling, but if you're using a deployment tool such as Kubernetes, I don't see why it wouldn't be fairly easy. And it might be a good idea to add a message in the admin UI if you all of your nodes are experiencing a high load.
By just looking at your max load over the last 24h or perhaps week, it would be pretty easy to see when to down scale.
That being said, as long as you remove the cockroach nodes one at a time , it's pretty easy to down scale a cockroach cluster.
.Net wasn't a priority due to our very limited resources. We will be expanding the number of drivers and ORMs greatly over the next while.
That being said, I tested npgsql a few days ago and it worked perfectly. Nothing too extensive, just created a db, 2 tables, inserted some data and did a join. So please give it a shot and if it doesn't work, file issues and we'll address them.
Cockroach Dev here.
We're actively working on a SQL layer actually.
We really need to update our github readme to contain info about it. It's under active development and of course, it's inspired by F1.
Cockroach dev here.
We're actually currently implementing a SQL layer within cockroach. So it wont' be layered, it's the main method of interaction with CockroachDB.
By just looking at your max load over the last 24h or perhaps week, it would be pretty easy to see when to down scale.
That being said, as long as you remove the cockroach nodes one at a time , it's pretty easy to down scale a cockroach cluster.