News for hackers. Stuff that matters.
Re:The trouble with Cassandra as an object storage metadata ... by pid_0 on Wednesday February 24, 2021 @10:00AM (#26250551)
From an ops perspective, managing Cassandra is a bitch. Just use a managed service unless you have the money to hire a dedicated Cassandra expert. I’m so glad I’m done with ops
Re:The trouble with Cassandra as an object storage metadata ... by mthomassen on Wednesday February 24, 2021 @11:49AM (#26252107)
Just to provide a counter statement; at $work we definatively do not have the appropriate headcount to even start considering running our own distrubuted datastores. However, we _do_ use Cassandra. And while many persons shared the sentiment of 'it being to hard to maintain' when the first few projects started to incorporate Cassandra, the truth is; there never has been any failure or incident, or even technical hurdle related to the usage/maintenance of the -admittedly smallish- Cassandra cluster (for 2 years now).

The costs of operating the cluster are ~5K/month (that's what our service provider charges us for 24/7 ops). I consider this a scam since averaged maintenance costs are perhaps ~1 hour per month.

(normally peaks at 40.000 writes/sec, 500 reads/sec, 200GB)

Re:The trouble with Cassandra as an object storage metadata ... by ddorian43 on Thursday February 25, 2021 @03:53AM (#26261004)
Yes, but 200GB and those read/write rates of data can reside in a single server even entirely in-memory, it's not a big amount.
Re:The trouble with Cassandra as an object storage metadata ... by XorNot on Wednesday February 24, 2021 @10:25AM (#26250842)
Also be wary with any company which "also does Cassandra" amongst a suite of products and isn't FAANG scale.

Chances are they absolutely don't have the headcount to properly manage it and were just filling out the portfolio they wanted to offer.