TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

CockroachDB license change

389 点作者 Cwizard9 个月前

59 条评论

AYBABTME9 个月前
I understand the goal, and the perceived abuse of the Core edition. But the problem with the Enterprise edition is that it&#x27;s quite expensive, &quot;contact us&quot; salesy, and it feels like taking a bite of this edition is possibly getting into bed with a future Oracle&#x2F;landlord type of relationship where you end up squeezed by your database vendor.<p>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&#x27;s was a way to walk back from it. But now there&#x27;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.<p>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?<p>I wish them the best, they&#x27;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.<p>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: <a href="https:&#x2F;&#x2F;aws.amazon.com&#x2F;blogs&#x2F;aws&#x2F;migration-complete-amazons-consumer-business-just-turned-off-its-final-oracle-database&#x2F;" rel="nofollow">https:&#x2F;&#x2F;aws.amazon.com&#x2F;blogs&#x2F;aws&#x2F;migration-complete-amazons-...</a>
评论 #41256788 未加载
评论 #41256767 未加载
评论 #41256806 未加载
评论 #41266608 未加载
评论 #41263285 未加载
评论 #41260350 未加载
评论 #41257784 未加载
评论 #41257748 未加载
评论 #41257399 未加载
评论 #41262726 未加载
评论 #41256680 未加载
评论 #41256774 未加载
评论 #41263012 未加载
jillesvangurp9 个月前
That&#x27;s another company that feels like they don&#x27;t want to be an OSS company after all. After Elastic, I pay more attention to contributor agreements. Basically I consider any project that requires transfer of copyright for OSS contributions as likely to change their license at some point. It&#x27;s fine; I&#x27;m not against that sort of thing and I sometimes pay for software. But I like to know what I&#x27;m getting into before and I don&#x27;t appreciate the bait and switch. It also guides decisions as to what I contribute to actively.<p>I do a simple sanity check with any OSS software before using it:<p>- Make sure there is no contributor agreement requirements. This is a gigantic red flag that the license can and probably will be changed at some point.<p>- Make sure the license is not overly restrictive (like AGPL). I appreciate people have good reasons for picking this license; but it comes with some serious restrictions in a commercial environment. And like it or not, a lot of companies have active policies against this. Either way, I avoid anything with this license.<p>- Make sure the project is actively maintained. You don&#x27;t want to get stuck with unmaintained software. Replacing dependencies is a PITA.<p>- Make sure the project is not overly dependent on VC funding. Startups fail all the time at which point anything they worked on turns into abandon ware.<p>- Ideally, make sure the project has a healthy diverse group of committers. Healthy here means more than one company is involved. Most projects that fail one or more of the above tests usually aren&#x27;t very healthy in this sense.
评论 #41258036 未加载
评论 #41257846 未加载
评论 #41257902 未加载
评论 #41257749 未加载
Thoreandan9 个月前
&gt; Does this mean that CockroachDB is no longer open source?<p>&gt; CockroachDB will remain source available under a new license. While the new license is a proprietary enterprise license, the source code will still be available for viewing and contributions.<p>The word you&#x27;re looking for is &quot;yes&quot;.
评论 #41266587 未加载
评论 #41258735 未加载
评论 #41264516 未加载
评论 #41257692 未加载
评论 #41257906 未加载
tschellenbach9 个月前
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...?
评论 #41256520 未加载
评论 #41256584 未加载
评论 #41256494 未加载
评论 #41259080 未加载
sho9 个月前
Probably a good move. I&#x27;d looked at Cockroach before for a project - they basically disqualified themselves from the start by nerfing the &quot;core&quot; 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.<p>This at least gets the full-fledged product in the door at startups. Say what you want about the timing or the BSL but I think this makes sense business-wise.
评论 #41256580 未加载
评论 #41267304 未加载
评论 #41256519 未加载
geenat9 个月前
Overall I feel like this is a step in the right direction.<p>I do love Cockroach, but the old licensing model was pretty brutal if you required any enterprise features (ex: incremental backup).<p>For reference, some other data stores doing &quot;horizontal scale of writes&quot; ..any others I&#x27;m missing ?<p>* MySQL: Vitess, Planetscale, TiDB, MariaDB Spider<p>* Postgres: Citus, YugabyteDB, YDB, Neon<p>* SQLite: mvsqlite, marmot<p>* Document: ScyllaDB, Cassandra, DynamoDB
评论 #41256799 未加载
评论 #41263155 未加载
评论 #41256754 未加载
评论 #41256515 未加载
评论 #41256392 未加载
评论 #41256541 未加载
评论 #41261985 未加载
ukuina9 个月前
&gt; On November 18, 2024, we will eliminate our Core offering and consolidate on a single, robust CockroachDB Enterprise license<p>That is incredibly short notice.
评论 #41256413 未加载
ezekg9 个月前
I posted it on Twitter, but I feel like revenue-based licensing models unnecessarily push the compliance burden onto the user. It&#x27;s an honor system, and even they admit it [0]; even Unity, who also uses a revenue-based model, admits it [1]. I&#x27;d prefer licensing models that are able to automatically segment users into customers at the software-level, such as a feature-based or usage-based model. For example, they could segment on CPU count or disk size, requiring an Enterprise offering for databases or clusters over a certain threshold.<p>But completely doing away with Core and requiring license keys even for free users [2] (which I assume is for revenue auditing purposes) ... I feel like that&#x27;s a big step backwards. All of this because their Enterprise offering seemingly wasn&#x27;t valuable enough (or from the comments -- it was too expensive).<p>I&#x27;d of focused there, on making Enterprise more valuable or more accessible, instead of doing something this drastic.<p>AFAICT, they&#x27;re also doing away with BUSL and DOSP [3], which is a big bummer.<p>[0]: <a href="https:&#x2F;&#x2F;techcrunch.com&#x2F;2024&#x2F;08&#x2F;15&#x2F;cockroach-labs-shakes-up-its-licensing-to-force-bigger-companies-to-pay&#x2F;" rel="nofollow">https:&#x2F;&#x2F;techcrunch.com&#x2F;2024&#x2F;08&#x2F;15&#x2F;cockroach-labs-shakes-up-i...</a><p>[1]: <a href="https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;Unity3D&#x2F;comments&#x2F;82mfwh&#x2F;how_could_unity_know_how_much_you_earn&#x2F;dvbc1fz&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;Unity3D&#x2F;comments&#x2F;82mfwh&#x2F;how_could_u...</a><p>[2]: <a href="https:&#x2F;&#x2F;www.cockroachlabs.com&#x2F;blog&#x2F;enterprise-license-announcement&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.cockroachlabs.com&#x2F;blog&#x2F;enterprise-license-announ...</a><p>[3]: <a href="https:&#x2F;&#x2F;opensource.org&#x2F;dosp" rel="nofollow">https:&#x2F;&#x2F;opensource.org&#x2F;dosp</a>
valyala9 个月前
VictoriaMetrics CTO here.<p>I don&#x27;t understand why pure open-source license such as Apache2, MIT or BSD should be replaced with some source available license in order to increase profits from enterprise support contracts:<p>- The license change won&#x27;t force cloud companies signing the enterprise agreement with you in most cases. If they didn&#x27;t want paying you before the license change, why they will change their mind after the licence change? It is better from costs and freedom perspective forking open-source version of your product and using it for free like Amazon did with Elasticsearch.<p>- The license change leads to user base fragmentation - some of your users switch to forks run by cloud companies. Others start searching for alternative open-source products. So, you start losing users and market share after the license change.<p>- The license change doesn&#x27;t bring you new beefy enterprise contracts, since it doesn&#x27;t include any incentives for your users to sign such contracts.<p>That&#x27;s why we at VictoriaMetrics aren&#x27;t going to change the Apache2 license for our products. Our main goal is to provide good products to users, and to help users use these products in the most efficient way. <a href="https:&#x2F;&#x2F;docs.victoriametrics.com&#x2F;goals&#x2F;" rel="nofollow">https:&#x2F;&#x2F;docs.victoriametrics.com&#x2F;goals&#x2F;</a>
评论 #41267222 未加载
评论 #41267128 未加载
steeeeeve9 个月前
I&#x27;m really not a big fan of holding backups and DR behind licensing. That&#x27;s base level functionality. That and row level security, but at least with row level, I get that there has been a lot of time and energy expended on that feature.<p>Cluster optimization, and enhanced security sure. And responsive support, absolutely.
评论 #41258831 未加载
评论 #41268154 未加载
Icathian9 个月前
So 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&#x27;m curious if there are some obvious big fish.
评论 #41256611 未加载
PeterZaitsev9 个月前
Finally all Open Source pretense is dropped. CockroachDB becomes Enterprise+Cloud database company with a free tier, not dissimilar from Oracle.<p>The revenue driver as a driver for freemium tier is interesting as it seems like it would require company to regularly disclose their revenue to CockroachDB which looks intrusive.
评论 #41257683 未加载
_joel9 个月前
Enforced telemetry for free users? That&#x27;s gross.
评论 #41256906 未加载
ko_pivot9 个月前
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.
评论 #41256571 未加载
tvink9 个月前
Free license:<p>&gt; Telemetry Required (excluding ephemeral clusters of 7 days or less)<p>So not free, then.<p>Is there already a popular fork?
评论 #41256640 未加载
评论 #41256757 未加载
评论 #41256460 未加载
评论 #41256457 未加载
th3w3bmast3r9 个月前
Yup - another &quot;Contact Us&quot; for pricing. God forbid if your business grows more than 10 Million ARR and now you owe them undisclosed amount of money.
评论 #41264016 未加载
osigurdson9 个月前
I think the reality is, only exceeding common codebases (Linux and Postgres for example), can survive with an open source model. If the value created by the product is 1M times greater than the costs, fine, a way to support it will materialize. Otherwise, economics take over and people need to get paid. The fact that source is publicly available is largely irrelevant.
评论 #41263429 未加载
jauntywundrkind9 个月前
You need an enterprise that&#x27;s already decided to use CockroachDB if your trial offer is only 30 days long. We&#x27;ve barely walked around the car &amp; kicked the tires before that trial runs out; it&#x27;s not respectful of the time it takes enterprises to move at all.
purpleblue9 个月前
I guess I don&#x27;t get it. CockroachDB is decidedly an enterprise product. There&#x27;s no need for even a medium sized company to require distributed database the likes of CockroachDB. If you&#x27;re a small company using it, you&#x27;re just using it for fun, and you&#x27;re probably not paying.<p>If you&#x27;re using it and paying for it, then this doesn&#x27;t seem like a problem. If you&#x27;re not using it, then it shouldn&#x27;t matter. If you&#x27;re using it but not paying for it, then maybe it&#x27;s okay that you have to start paying for it.
评论 #41266703 未加载
mehulashah9 个月前
It seems a shame that to grow, companies are backing away from the vector that got them there: open source.<p>I agree that current cloud providers are gaining more benefit from open source than they&#x27;re putting in. So, it seems logical that the main developers want to recapture some of that.<p>On the other hand, open source is supposed to help build a bigger pie. If the pie gets bigger faster (i.e. more people using CockroachDB) then is the recapture worth it?<p>It seems the smaller companies think so. But, I don&#x27;t know of a solid analysis that shows this to be true.
pianoben9 个月前
Wow, what a rug-pull! Good luck to Cockroach Labs, but I doubt their product is entrenched-enough to make this strategy sustainable - it&#x27;s going to _kill_ growth.
WuxiFingerHold9 个月前
It&#x27;s a surprising and very welcome change. Most will benefit.<p>If you have more than $10M revenue, why on earth would you run the limited open core version of CochroachDB just to save some $1K-$10K (which is about the enterprise license cost). The open core version has limitations you don&#x27;t want to miss esp. reg. backup and restore, encryption, follower reads. Now all those features are available for free if you&#x27;re small.
评论 #41266648 未加载
评论 #41354964 未加载
dilyevsky9 个月前
Anyone here migrated to TiDB from cockroach and can share experience? Asking for a friend…
评论 #41258612 未加载
timenova9 个月前
I&#x27;m guessing the Required Telemetry thing is gonna cause a technical&#x2F;security problem too. Most production databases would be running in private isolated networks with no inbound or outbound internet access on the VMs, and because of this requirement, they&#x27;ll have to open outbound access to at least Cockroach&#x27;s IPs.
emocin9 个月前
I worked with the cockroachdb founders at a previous company.<p>They’re clowns.
ThinkBeat9 个月前
I am a great fan of scaling vertically as far sa possible on DB servers. These days that is pretty damn high. It avoids a lot of prickly edge cases.<p>It is definitively not one solution for all. There are many cases where it just won&#x27;t work.<p>I would like to see more IBM Z servers being used. $$$$$$$$ though
评论 #41257907 未加载
indulona9 个月前
If you prefer mysql sql flavour, pingcap has titanium db(tidb) alternative.
9999000009999 个月前
I&#x27;m trying to figure out how this is better than Postgress ?<p>Does it perform significantly better to justify the cost? Back in the day I worked heavily with databases and we always tilted towards open source.
评论 #41257543 未加载
评论 #41257316 未加载
评论 #41312943 未加载
评论 #41263227 未加载
joeblubaugh9 个月前
&gt; Even by conservative estimates, the vast majority of the world’s businesses will meet the eligibility requirements for the Enterprise Free Tier license<p>This feels dishonest. What percentage of the world’s business need a system like CockroachDB? Of those, what percentage are under 10 million in revenue?
评论 #41258663 未加载
rnavi9 个月前
Amidst the frequent noise - its hard to notice that even the most stringent of OSS licenses like AGPL was written way back in 2002! Cloud was not even in the picture. Since then, ever growing cloud players have been playing the &#x27;state&#x27; role and misusing OSS as &#x27;religion&#x27; heavily affecting infra OSS products or companies.
simonebrunozzi9 个月前
I spotted this company in their seed stage and wanted to invest. The founders asked us to provide names for reference checks, etc - a bit unusual, but we were almost done with the commitment, so why not?<p>After quite a lot of work, introductions, and back and forth, they told us: sorry, Google Ventures is investing and we&#x27;re kicking everyone else out, despite we expected an allocation at that point (50k, not very large). Not nice by them, and not nice by GV, but... Just another lesson learned in the epicenter of startup investing which is San Francisco. This was Feb 2015. Wow, almost 10 years ago. Time flies.<p>I am still happy to see they&#x27;ve been successful at building the company. I loved the product from the very beginning.
zeeZ9 个月前
The FAQ that asks &quot;What telemetry data will be collected, and how will it be used?&quot; never answers the first half of the question in its marketese blurb. You failed the &quot;ask yourself a question and answer it&quot; part of the exam.
scblock9 个月前
Dancing around the &quot;so it&#x27;s not open source&quot; by not clearly saying &quot;correct, it&#x27;s no longer open source&quot;.<p>&quot;CockroachDB will remain source available under a new license&quot; sounds correct but it&#x27;s still sidestepping the question. And &quot;the source code will still be available for viewing and contributions&quot; is completely shit. Why would anyone contribute to a commercial product unless they&#x27;re getting paid to do so.<p>Also, the use of this kind of &quot;evolving our&quot; and &quot;advancing our&quot; phrasing is so incredibly gross. No one speaks like this except in corporate announcements.
评论 #41256991 未加载
评论 #41257367 未加载
评论 #41257951 未加载
评论 #41256608 未加载
tristor9 个月前
I like the technology here, but at the same time I feel like they&#x27;ve been on this trajectory since the beginning. It&#x27;s just another VC-backed company using open source for marketing, without any legitimate desire to actually be open source. At least now they&#x27;ve pulled the wool off of it.
vinay_ys9 个月前
This made me wonder about postgres. Is Postgres at risk of being taken over by some corporate? What can we learn from all these free open-source databases that has gone enterprise commercial.
评论 #41263119 未加载
评论 #41265389 未加载
redwood9 个月前
I just don&#x27;t understand why they didn&#x27;t go with a copyleft license like SSPL; is it because they&#x27;re worried too many people will self-manage in the Enterprise and not pay them?
JonChesterfield9 个月前
Ensure your data is secure with our mandatory telemetry. No deal.
OptionOfT9 个月前
WRT CockroachDB Enterprise Free&#x27;s telemetry requirement:<p>&gt; Required (excluding ephemeral clusters of 7 days or less)<p>Does that mean the cluster will stop working when it can no longer report?
评论 #41263478 未加载
paxys9 个月前
I get wanting large companies and cloud providers to pay, but mandatory telemetry collection in the self-hosted version of the product is an absolute non starter.
rmoriz9 个月前
How to comply with telemetry in air-gapped environments?
评论 #41257504 未加载
xnx9 个月前
What are the remaining use cases for CockroachDB where there isn&#x27;t a better&#x2F;open-source alternative?
评论 #41257263 未加载
评论 #41259670 未加载
Havoc9 个月前
Are any of the databases certain (as certain as one can be) to stay open?
评论 #41267120 未加载
cynicalsecurity9 个月前
I&#x27;ve never seen this database used by anyone in real life.
评论 #41258875 未加载
评论 #41257470 未加载
dzonga9 个月前
predictable and pretty good business move.<p>these things are easy to evaluate - 1. what&#x27;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 -&gt; vitess since those products don&#x27;t come from a database vendor. mongo might qualify too
评论 #41256842 未加载
tbarbugli9 个月前
<a href="https:&#x2F;&#x2F;github.com&#x2F;cockroachdb&#x2F;cockroach&#x2F;graphs&#x2F;contributors">https:&#x2F;&#x2F;github.com&#x2F;cockroachdb&#x2F;cockroach&#x2F;graphs&#x2F;contributors</a>
486sx339 个月前
It seems cockroach was aptly named
hnarn9 个月前
It&#x27;s honestly getting tiresome reading about yet another company that rides on the wave of open source for popularity and growth, but only for as long as it suits their own bottom line. Just like every other example, the page is filled to the brim with borderline unparsable marketing speak and, excuse my french, pure bullshit. Here&#x27;s an example:<p>&gt; we are updating our licensing model to better serve our diverse community of users<p>One could hope that whoever wrote this at least had the decency to blush while doing so. So here&#x27;s what&#x27;s actually happening, as I understand it at least:<p>CockroachDB <i>used to be</i> split into &quot;Core&quot; and &quot;Enterprise&quot;. Core was Apache 2.0 licensed (open source), Enterprise was BSL (fake open source, &quot;source available&quot;, bullshit). After three years, BSL code becomes real open source. This setup that they are sunsetting is already pretty restrictive, and is by no means uncontroversially &quot;open source&quot;.<p>The New And Improved(tm) idea they have to &quot;better serve&quot; their &quot;diverse community of users&quot; is even worse: it&#x27;s free as in beer to use, but other than that it&#x27;s completely proprietary, and it also includes *mandatory telemetry* for non-paying users. Any reference to &quot;open&quot; in regards to this product is a complete lie, because being able to read the source code does not make a product open source -- Microsoft allows you to read their code too, if you sign a piece of paper with them.<p>I&#x27;ve never used CockroachDB, but I&#x27;m glad I saw this, because now I know there&#x27;s a 0% chance I will ever consider using it.
评论 #41265038 未加载
hannob9 个月前
I like this part:<p>&quot;4. Does this mean CockroachDB is no longer open source?<p>CockroachDB will remain source available under a new license. While the new license is a proprietary enterprise license, the source code will still be available for viewing and contributions.&quot;<p>I mean... &quot;The answer is kinda sorta &#x27;No&#x27;, but we really would prefer not to phrase it like that.&quot;
评论 #41264002 未加载
Aeolun9 个月前
Mandatory telemetry?
znpy9 个月前
Friendly reminder that if you contributed code but signed a contribution agreement (which assigns copyright on the code contribution to cockroachlabs) you’ve got nothing to complain about.<p>Never sign contributions agreement: it will be used against you when the license inevitably get changed.
PaywallBuster9 个月前
at least should still cover a lot of businesses under the free tier<p>&gt; Individuals and businesses, under $10M in annual revenue, can use CockroachDB Enterprise for free
评论 #41256750 未加载
Eumenes9 个月前
They&#x27;re following the Mongo playbook
GiorgioG9 个月前
Yeah no thanks, I&#x27;ll stick with Postgres
djaouen9 个月前
Thank God I stuck with Postgres lol
victorbjorklund9 个月前
another open source project has died. At least we will always have Postgres.
alexvitkov9 个月前
I&#x27;m not even going to read this, we all know what it is and we all know it&#x27;s just the first step in a long series of very shitty changes, expect all new development to be in the &quot;contact us&quot; tier.<p>Ignorance was maybe excusable the first 15 times, but if you keep falling for corporate owned rug-pull OSS packages in 2024, you deserve what&#x27;s coming for you.<p>Weird databases are NFTs for startup founders. You&#x27;re not too cool for Postgres. Use it.
评论 #41261651 未加载
评论 #41260328 未加载
评论 #41260403 未加载
评论 #41258825 未加载
kelsey987654319 个月前
Another database fails to be better and ends up worse. This is why we use DAL agnosticism.
h_tbob9 个月前
I always use good ol’ MySQL. If anything happens can hop to Maria
jappgar9 个月前
&quot;Open-source&quot; in 2024 is a synonym for &quot;ransomware.&quot;<p>It&#x27;s still nice that I can audit the code and contribute (unpaid) changes, but I no longer assume anyone is acting in good faith.
评论 #41259221 未加载