I’ve run more Cassandra than anyone on the planet. Also more FoundationDB. And more Postgres than I can count. Likely 3 orders of magnitude more than you.
1. Any db at that scale requires a team. Thousands of cores is gonna be either paying saas or paying a team and I don’t care what the tech is. You’re gonna fuck up any db on the market letting your app eng run a thousand cores of Postgres or MySQL or couchbase or cockroach or tidb.
2. Cassandra at scale has a demonstrably better cost and availability slo than literally annything else I’ve ever tried to run, as long as you have a competent team. And I had a great team. But we had a great team because we understood that at million core scale it’s a core of the product and you invest in your core. But a good team of a dozen people can run a million cores at 6-8 nines, at lower cost per byte or cost per query than any db-aas you can buy online from any cloud vendor. I know this because we checked, and I’ve been ahead every time.
3. The db isnt fun to run. But it’s getting way better. If you think this is 2009, it’s not. The folks working on it in 2026 know what they’re doing and the last decade has made it measurably safer and easier.
Nothings free, but I’d bet my salary I can run damn near any company on Cassandra cheaper than any of your alternatives. Even all the vendors who keep selling against Cassandra. A competent team on Cassandra is going to beat your vendor product 90% of the time.
What exactly is your point, besides the self aggrandising? None of this is news to anyone, but I'm sure we're all glad to hear you're so shit-hot at everything.
> 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
It's illegal to pass a school bus when the lights are on / stop arm is extended. That's why they have the stop-sign on the driver's side of the bus.
The article forgot to mention that but the assumption is that (a) a reasonable driver would know that and (b) their audience probably remembered that happening, since it was only a few months ago IIRC.
Yes! When they are letting kids off it becomes a defacto crosswalk where kids might come out to cross the street in front of the bus but you can't see them because of the bus itself blocking your view.
Many school buses have stop signs that extend when they have the doors open to help remind people of this and prevent the little overzealous street crossers from getting splattered.
Ah I see thank for the explanation! That makes sense. We don't really get school buses here, kids go to school on the bike or here in the city by metro. (Or the parents drop them off of course).
> 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.
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.
> 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++.
Yes, I understand they looked at the source and re-implemented a bunch of it when they started 10 years ago. But in the result it's a very different code. I mean, it's 45K commits so I believe they implemented things by themselves in majority of those commits. I guess we just have different understanding of the copycat term.
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.
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.
I’ve run more Cassandra than anyone on the planet. Also more FoundationDB. And more Postgres than I can count. Likely 3 orders of magnitude more than you.
1. Any db at that scale requires a team. Thousands of cores is gonna be either paying saas or paying a team and I don’t care what the tech is. You’re gonna fuck up any db on the market letting your app eng run a thousand cores of Postgres or MySQL or couchbase or cockroach or tidb.
2. Cassandra at scale has a demonstrably better cost and availability slo than literally annything else I’ve ever tried to run, as long as you have a competent team. And I had a great team. But we had a great team because we understood that at million core scale it’s a core of the product and you invest in your core. But a good team of a dozen people can run a million cores at 6-8 nines, at lower cost per byte or cost per query than any db-aas you can buy online from any cloud vendor. I know this because we checked, and I’ve been ahead every time.
3. The db isnt fun to run. But it’s getting way better. If you think this is 2009, it’s not. The folks working on it in 2026 know what they’re doing and the last decade has made it measurably safer and easier.
Nothings free, but I’d bet my salary I can run damn near any company on Cassandra cheaper than any of your alternatives. Even all the vendors who keep selling against Cassandra. A competent team on Cassandra is going to beat your vendor product 90% of the time.