> Waymo is now completing 450,000 weekly driverless rides across six cities, with a peer-reviewed study showing statistically significantly lower crash rates than human drivers across 56.7 million rider-only miles. When Waymo’s vehicles were caught passing school buses, the company filed a voluntary recall within weeks. Tesla, on the other hand, is now on its second deadline extension just to tell NHTSA about FSD’s traffic violations.
That, in itself, is saying more than anything else
Youre not far off, just use your original sentence and acknowledge that Scylla isn’t the OSS here, its the company that came in, forked a volunteer driven project, and tried to pretend its theirs:
> Or more often companies with money come to fork an open source project from the developer, and continue pretending it's their own now.
> Copycat is a bit of a stretch here imho, considering it's in different language, and even the general architecture. But I agree they are very compatible on the protocol level, which they used as an advantage as people don't need to rewrite their code when they migrate
It's not a stretch. They literally copied the java code and re-implemented it class-by-class with Seastar/c++.
> I would say it's opposite. No one contributes to open source and the developers have to make money on the side to work on the project
You missed the important part of his sentence:
> All those open source copycat projects, using open source to get exposure then switching
The original open source here was Cassandra. Scylla exists to pick off that market share. They launch with a free license, pull customers, then swap license. The actual adoption of Scylla would have been a fraction had it been released under this license to start, which everyone understands.
> Or more often companies with money come to fork an open source project from the developer, and continue pretending it's their own now
It had already been AGPL, so it's not like they're protecting against competition. They already had a license that avoided the forking problem. This isn't protection against AWS (keyspaces likely has more OSS cassandra code in the protocol tier than it has Scylla code, if it has either). It's protection against free consumption.
Regrettably the folks who have been using it for years aren’t going to be give a lot of specifics, but generation of k8s yaml / jsonnet in particular was exceptionally common. One example from the other thread:
> My team migrated several kloc k8s configuration to pkl with great success. Internally we used to write alert definitions in pkl and it would generate configuration for 2 different monitoring tools, a pretty static documentation site and link it all together nicely.
That database spent 3-4 years primarily focused on correctness from 2018-2022.
The industry moves fast, our memories are slow. But there are millions of instances of cassandra in production across most of the fortune 500, and half of this thread has never heard of RavenDB
It’s disappointing to me that the technologist desire to experiment with new DBs continually puts naive customers at correctness and durability risk they don’t (won’t) understand.
> Apple's underlying economics haven't changed, so they have not had any reason to over-hire in the first place.
The bloomberg article has a visual showing revenue-per-employee going up from 1.17M/employee (2017-2019) to 2.51M/employee (2020-2022), so ... some of the underlying economics changed somehow?
Cassandra is very good when all of these are true:
- You're willing to give up some common SQL-isms for leaderless, multi-dc, high-availability
- You're going to grow to need more than one machine taking writes - if you can fit on one normal commodity machine, just use something designed for one machine. Cassandra sacrifices a lot to scale to ~thousand-machines-per-cluster, so if you can use one machine, don't bother with Cassandra.
- You can model your data in a way that does SELECTs without JOINs, and always uses AT LEAST the partition key in the WHERE clause. Denormalizing and duplicating your data is PROBABLY ok.
- You're willing to run Java (so you understand that you may need to tune the JVM eventually), and you're willing to learn about data modeling before you just start writing code
If all of that is true, Cassandra starts being interesting.
That, in itself, is saying more than anything else