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 t…
CockroachDB license change
41–50 of 476 posts
Re: CockroachDB license change
#42these things are easy to evaluate - 1. what's your appetite in running infra ? low - then use the SAAS offering 2. doable - then use a db that has good scalable solutions in this case mysql -> vitess since those products don't come from a database vendor. mongo might qualify too
Re: CockroachDB license change
#43Re: CockroachDB license change
#44Does it perform significantly better to justify the cost? Back in the day I worked heavily with databases and we always tilted towards open source.
Re: CockroachDB license change
#45at least should still cover a lot of businesses under the free tier > Individuals and businesses, under $10M in annual revenue, can use CockroachDB Enterprise for free
Plenty of us have had to deal with this scenarios before with Oracle. Cheap or free to get started, then your product takes off and Oracle shows up and starts to demand their cut. I'm not suggesting that Cockroach is the new Oracle, but this type of licensing introduces a significant uncertainty into your future plans.
Re: CockroachDB license change
#46Overall 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…
Re: CockroachDB license change
#47Free license: > Telemetry Required (excluding ephemeral clusters of 7 days or less) So not free, then. Is there already a popular fork?
Re: CockroachDB license change
#48Earlier quoted context omitted.
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.
if nobody forked it five years ago, they probably aren't going to fork it now
if somebody did fork it five years ago, they probably aren't going to try to merge in new source code drops as they convert to open source
Re: CockroachDB license change
#49I 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…
As always: “If you have to ask, you can’t afford it.”
Re: CockroachDB license change
#50I 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…