3 ms·
Why are you recommending S3 when Ceph exists? You almost literally just throw hard drives at it and it gives you remote block devices for VMs, a NFS style share
by Spivak 5y ago
Why are you recommending S3 when Ceph exists? You almost literally just throw hard drives at it and it gives you remote block devices for VMs, a NFS style shared FS, and an S3 client compatible object store.
- Eikon 5y agoWhat? Operating a small ceph cluster is almost a full time job, at least if you care about your data...
- Spivak 5y agoPeople always think Ceph is super complicated but I promise you it isn't. I worked at a place where my (3 person) team and I operated a 1 PB Ceph cluster replicated across two datacenters along with literally every other service needed to run a production web app. It was one of the lowest maintenance services we deployed -- Kafka and our RabbitMQ clusters were the things that always gave us trouble.
- krab 5y agoI was on a team that had a tiny (a few GBs) Ceph cluster because it was the easiest option for high availability of these files that we really wanted to have on premise. There were never any issues so I can believe what you're saying. Still, for the amount of data I work with, the cloud storage usually wins.
- krab 5y agoOthers may have other preferences. This is what worked for me. I just find S3 quite cheap for storing a few (tens of) terabytes plus some glacier archives. For data I often want multiple locations redundancy and encryption. That gets more complicated than what I can save. I guess the equation changes when you have more data or looser requirements. That's actually my point. It's very hard to recreate the whole AWS experience, but it's quite possible to pick any piece and do it much cheaper.