Free license: > Telemetry Required (excluding ephemeral clusters of 7 days or less) So not free, then. Is there already a popular fork?
This is really painful, I don't want this pattern of data collection being common, Telemetry included.
CockroachDB license change
11–20 of 476 posts
Re: CockroachDB license change
#12Free license: > Telemetry Required (excluding ephemeral clusters of 7 days or less) So not free, then. Is there already a popular fork?
it hasn't been open-source since 02019 according to https://en.wikipedia.org/wiki/CockroachDB#History so if there are popular forks they'd have to be five years old
Re: CockroachDB license change
#13So the obvious question is, which big shops were using the Core version that ended up prompting this change? I know of one or two but I'm curious if there are some obvious big fish.
Re: CockroachDB license change
#14As much as this has the vibes of a classic OSS rug pull, as a Cockroach user, I don’t really take it that way. First of all, it was already not open source and secondly, the free to use version was missing key features like follower reads and incremental backups.
Re: CockroachDB license change
#15> On November 18, 2024, we will eliminate our Core offering and consolidate on a single, robust CockroachDB Enterprise license That is incredibly short notice.
only a problem if you need to update
even then you've had five years notice that enshittification was coming: https://en.wikipedia.org/wiki/CockroachDB#History
Re: CockroachDB license change
#16We will probably end up removing CockroachDB from our infra due to this change. It also makes me a bit worried about their long term viability. How much ARR does CockroachDB have and what was their last round valuation...?
What will you switch to? I feel like there isn’t a good alternative.
Re: CockroachDB license change
#17Dancing around the "so it's not open source" by not clearly saying "correct, it's no longer open source".
"CockroachDB will remain source available under a new license" sounds correct but it's still sidestepping the question. And "the source code will still be available for viewing and contributions" is completely shit. Why would anyone contribute to a commercial product unless they're getting paid to do so.
Also, the use of this kind of "evolving our" and "advancing our" phrasing is so incredibly gross. No one speaks like this except in corporate announcements.
Re: CockroachDB license change
#18Overall I feel like this is a step in the right direction. I do love Cockroach, but the old licensing model was pretty brutal if you required any enterprise features (ex: incremental backup). For reference, some other data stores doing "horizontal scale of writes" ..any others I'm missing ? * MySQL: Vitess, Planetscale, TiDB, MariaDB Spider * Postgres: Citus, YugabyteDB, YDB, Neon * SQLite: mvsqlite, marmot * Documen…
> if you required any enterprise features
For me it was the multiple regions. It's like.. with that disabled why are we even here? Data residency is the whole point...
Re: CockroachDB license change
#19Probably a good move. I'd looked at Cockroach before for a project - they basically disqualified themselves from the start by nerfing the "core" version so bad it was useless, while Enterprise was some absolutely insane figure for a cash-strapped startup. While it was possible to hotfix the code to get around their restrictions - we eventually just used something else. This at least gets the full-fledged product in t…
What did you use instead?
Re: CockroachDB license change
#20We will probably end up removing CockroachDB from our infra due to this change. It also makes me a bit worried about their long term viability. How much ARR does CockroachDB have and what was their last round valuation...?
CockroachDB is easier to manage and more cost effective than Postgress due to that. But now I suspect the balance tips back to Postgres