4 ms·
This looks almost exactly like the kind of data store I need for an application. I have previously considered using minio (too inflexible wrt to adding more sha
by heipei 6y ago
This looks almost exactly like the kind of data store I need for an application. I have previously considered using minio (too inflexible wrt to adding more shards / replicas), a homebrew system based on something like ScyllaDB (needs code on top to act like a blob store) or S3/B2 (too slow and/or expensive wrt to transfer costs). Is anyone using this in production and can share a story of how stable and hard to run it is?
- drenvuk 6y agoScylla wouldn't even be good for blob store if you're dealing with megabytes. If you're dealing with kB range Cassandra is stabler and pretty much what you want. For big (MB+) Seaweed is up there for the best option.
- heipei 6y agoYes, this is another reason that kept me from doing it. I have on class of files (images) that go from 1kB to ~ 1MB in size, but never above. But then I have another set of files that go from 1B to several MB in the worst case (with a normal distribution around 13kB). Ideally I'd like to have one store that can handle all of these so I don't have to worry about worst-case performance too much.
- dragonsh 6y agoLike you we also started with minio, but as it was not fully S3 compatible (list folders and few more related S3 API) and do not have FUSE or NFS support either. So we started moving our infrastructure to seaweedfs. We have not completed the move yet, once done might share some benchmarks. Some of the benchmarks you can also see on their GitHub project.
- 3np 6y agoHave you looked at Ceph?
- PeterCorless 6y agoFun fact: Ceph is being rebuilt with the core engine of Scylla, Seastar, at its heart: https://docs.ceph.com/en/latest/dev/seastore/ https://docs.ceph.com/en/latest/dev/seastore/