Live data from Hacker News

CockroachDB license change

cockroachlabs.com

21–30 of 476 posts

Re: CockroachDB license change

#21
post #3

Overall 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…

The only thing I don't like is the mandatory telemetry.

Re: CockroachDB license change

#22

As 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.

Someone creating free software and changing the license on software they created isn't a "rug pull" in any sense of the word. You paid $0 and contributed nothing. What rug is being pulled?

A rug pull is when you buy into something and then it's taken away, like when a cryptocurrency token is busted out or you spend money on something and then it's cancelled or nerfed.

Don't like it? Write your own distributed fault tolerant database, or contribute an extension for Raft replication to the Postgres open source code base.

Re: CockroachDB license change

#23
post #10

Probably 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…

The enterprise per core is still an insane figure, based on last time I interacted with sales- would be amazing if this was revised, too, to be more competitive with Planetscale, etc.

Would be far easier to recommend CockroachDB if it were more competitive with Planetscale.

Re: CockroachDB license change

#24

We 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 issue do you have with the changes? Sounds like it's mostly focused on making it more affordable for small operations.

Re: CockroachDB license change

#25
post #12
post #4

Free 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

BSL code automatically converts to open source at a specified date. So probably several releases since then are now as open source as anything else in the world. And if not, then they will be soon - BSL allows a maximum 5 year delay.

Re: CockroachDB license change

#26
post #17

Dancing 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, th…

> Why would anyone contribute to a commercial product unless they're getting paid to do so.

Because they get to use it for free?

Re: CockroachDB license change

#28
I understand the goal, and the perceived abuse of the Core edition. But the problem with the Enterprise edition is that it's quite expensive, "contact us" salesy, and it feels like taking a bite of this edition is possibly getting into bed with a future Oracle/landlord type of relationship where you end up squeezed by your database vendor.

The Core offering made this palatable, one could fallback to Core features if the relationship with Cockroach Labs degraded, which made it possible to entertain the Enterprise license since there's was a way to walk back from it. But now there's no such mitigation available. By using non-PG native features, users of the Enterprise edition are accepting to get in bed with Cockroach Labs for effectively forever (databases), a single provider that has no competition.

I think this may backfire, as it now seems imprudent to go all in on Cockroach Labs. They may be nice folks today, but who knows who will run the place in 5y when the next round of squeeze comes?

I wish them the best, they're a great team and I always liked the project and toyed with it for years, and currently am involved with a paid Enterprise license. But this change in the dynamics is really giving me pause.

Getting in bed with a single vendor for an incredibly sticky tool comes with a _lot_ of risk. It took at least 17y for Amazon to get rid of its last Oracle database: https://aws.amazon.com/blogs/aws/migration-complete-amazons-...

Re: CockroachDB license change

#29

We 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

Citus would be great if the HA story was better: https://github.com/citusdata/citus/issues/7602

Re: CockroachDB license change

#30
post #16

We 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.

YugabyteDB is a commonly used alternative.
Post reply on HN