I'm not sure I'd suggest building a single DIY Backblaze pod. The SATA
port multipliers are a pain both from a supply chain and systems management
perspective. Can be worth it when you're amortizing that across a lot of
servers and can exert some leverage over wholesale suppliers, but less so
for
This is off-topic. But if your goal is to maximise storage density and
also ensuring data durability and availability, this is what you should
be looking at:
* hardware:
https://www.backblaze.com/blog/open-source-data-storage-server/
* architecture and software:
https://www.backblaze.co
I am also curious on this question. Say your use case is to store
10PBytes of data in a new server room / data-center with new equipment,
what makes the most sense? If your database is primarily write with
little read, I think you'd want to maximize disk space per rack space.
So you may opt
I'm sure there's a lots of pitfalls. A few of them in my mind right now:
* With a single node, you will completely lose the benefit of high
availability from Cassandra. Not only hardware failure will result
in downtime, routine maintenance (such as software upgrade) can also
result in d
Hi, one project I wrote is using Cassandra to back the huge amount of
data it needs (data is written only once and read very rarely, but needs
to be accessible for years, so the storage needs become huge in time and
I chose Cassandra mainly for its horizontal scalability regarding disk
size) an
Thanks, Piotr & team. Fantastic contribution!
I'll request Constantia.io to get in contact with you to shortlist it in
next month's Changelog blog post. Cheers!
I am pleased to announce the first release of a brand new, asynchronous
CQL driver for Rust, fully compatible with Apache Cassandra™ - Scylla
Rust Driver 0.1.0.
Our new driver is capable of the following, and much more:
* Asynchronous API based on Tokio (tokio.rs)
* Token-aware routing
* Sha
