Good for CockroachDB, they need to make money. I understand I'm not their target user though, I stopped using them when they released Follower-Reads as an enterprise feature.
I'm back to Postgres for now but I can't stop thinking about the opportunity CRDB is missing by not releasing the enterprise features as part of the BSL-licensed core, that way I can use them from the very beginning(when I have no money) and when I grow and have traction, money and what not, then I can pay to scale beyond X amount of nodes/capacity a la MemSQL[0].
> I stopped using them when they released Follower-Reads as an enterprise feature.
I read Cockroach Labs’ strategy to be good on single nodes, great on single-datacentre cluster, phenomenal worldwide.
They offer single-DC features open-source, and worldwide enterprise-only.
Apart from SQL features, their open-source cluster offer seems superior to PostgreSQL. Sure, they do not have follower-reads, but neither does PG (which does not even have AS OF SYSTEM TIME, a prerequisite), and it is only beneficial with multi-DC.
Reads are still distributed by range, so there is no particular negative compared to Postgres.
I'm not necessarily exhausting the physical capacity of a single datacenter to expand to another datacenter, I may expand early or from day one to run queries closer to the user even if the workload is a few seconds behind. I don't think Follow-the-workload works well for that scenario.
I'm back to Postgres for now but I can't stop thinking about the opportunity CRDB is missing by not releasing the enterprise features as part of the BSL-licensed core, that way I can use them from the very beginning(when I have no money) and when I grow and have traction, money and what not, then I can pay to scale beyond X amount of nodes/capacity a la MemSQL[0].
[0] https://www.memsql.com/blog/announcing-memsql-free-tier/