News for hackers. Stuff that matters.
Re:Introducing “Database Performance at Scale”: A Free, Open... by bastawhiz on Thursday October 05, 2023 @01:25PM (#37781352)
There are lots of tradeoffs when choosing Cassandra:

1. If you delete data, tombstones are a problem that nobody wants to have to think about.

2. Denormalizing data instead of joining isn't always practical or feasible.

3. If you're not dealing with large amounts of data, Postgres and MySQL are just easier. There's less headache and it's easier to build against them.

4. One of the big advertised strengths of Cassandra is handling high write volume. Many applications have relatively few writes and large amounts of reads.

Re:Introducing “Database Performance at Scale”: A Free, Open... by pmcf on Thursday October 05, 2023 @04:04PM (#37783594)
Fast writes and slow reads was true in 2012. The project has been busy since.
Re:Introducing “Database Performance at Scale”: A Free, Open... by bastawhiz on Friday October 06, 2023 @10:24AM (#37791188)
Fast reads are commonplace. Having fast writes for a workload without an especially high volume of writes is not selling anyone on a database.
Re:Introducing “Database Performance at Scale”: A Free, Open... by swingingFlyFish on Monday October 16, 2023 @11:07PM (#37910078)
Unless it's a commenting system ;)