13 comments

[ 4.6 ms ] story [ 40.2 ms ] thread
no one will honor this license

commercial users know full well a team of less than ten people can never hope to track down license violators while still doing dev work

IMO, the only way that would be possible is if they buried some kind of telemetry in their code. I don't support that kind of thing, but you could also pass that off to investors as "trying".
I don't think most commercial users are in the business of purposefully breaking licensing agreements. Even small startups have to worry about this because it generally comes up in due diligence for VC investment. The risk of a future lawsuit, even if small, generally outweigh the savings.
That's a great problem to have for a startup. "We have a ton of use that we can see through these proxy metrics, so the goal of this series c is, in addition to continuing to innovate on a product side, start investing in license auditing of companies that can't meaningfully change to another product quickly" is a pretty great pitch a few years down the line.
Unless you die because of a lack of revenue first.
I’ve yet to see someone not terrified of redis cluster mode. Everyone wants to jump ship for some new product. In a decade of defending Redis from “buzzwordDB” replacements (its multi threaded!!!) I’ve not heard a single reasonable argument against Redis. Did Aerospike destroy Redis yet?

Good luck dragonfly - and congrats on the raise - but you’ll have to pry reliable Redis from my cold dead hands!

> The jury’s out on that — TechCrunch can’t independently confirm those claims. But for what it’s worth, the open source Dragonfly, which reached version 1.0 this week, already has some uptake — and investment.

Its not open source, the BSL is not an open source license, rather a source available one.

I thought KeyDB already provided what Dragonfly claims to do except better?