31–40 of 147 posts
SeaweedFS is great as well. https://github.com/seaweedfs/seaweedfs
Tried this for my own homelab, either I misconfigured it or it consumes x2(linearly) memory(working) of the stored data. So, for example, if I put 1GB of data, seaweed would immediately consume 2GB of memory constantly! Edit: memory = RAM
What is the difference between a "distributed object storage" and a file system?
Earlier quoted context omitted.
Sending your api key in the header is equivalent to basic auth.
This is not intended for commercial services. Realistically, this software was made for people who keep servers in their basement. The security profile of LAN users is very different than public AWS.
I have used Garage for a long time. It's great, but the AWS sigv4 protocol for accessing it is just frustrating. Why can't I just send my API key as a header? I don't need the full AWS SDK to get and put files, and the AWS sigv4 is a ton of extra complexity to add to my projects. I don't care about the "security benefits" of AWS sigv4. I hope the authors consider a different authentication scheme so I can recommend G…
I read that curl recently added sigv4 for what that’s worth[0] 0: https://how.wtf/aws-sigv4-requests-with-curl.html
I find it interesting that they chose CRDTs over Raft for distributed consensus.
SeaweedFS is great as well. https://github.com/seaweedfs/seaweedfs
Tried this for my own homelab, either I misconfigured it or it consumes x2(linearly) memory(working) of the stored data. So, for example, if I put 1GB of data, seaweed would immediately consume 2GB of memory constantly! Edit: memory = RAM
https://github.com/cycneuramus/seaweedfs-docker-swarm/blob/m...
I feel like a lot of complexity and performance overhead could be reduced if you only store immutable blobs under their hash (e.g Blake3). Combined with a soft delete this would make all operations idempotent, blobs trivially cacheable, and all state a CRDT/monotonically mergeable/coordination free.
There is stuff like IPFS in the large, but I want this for local deployments as a S3 replacement, when the metadata is stored elsewhere like git or a database.
What I'm really missing in this space is something like this for content addressed blob storage. I feel like a lot of complexity and performance overhead could be reduced if you only store immutable blobs under their hash (e.g Blake3). Combined with a soft delete this would make all operations idempotent, blobs trivially cacheable, and all state a CRDT/monotonically mergeable/coordination free. There is stuff like IP…
They probably don't expose it publicly though.
We got ceph, minio, seaweedfs ... and a dozen of others. I am genuinly curious what is the goal here?
I have used Garage for a long time. It's great, but the AWS sigv4 protocol for accessing it is just frustrating. Why can't I just send my API key as a header? I don't need the full AWS SDK to get and put files, and the AWS sigv4 is a ton of extra complexity to add to my projects. I don't care about the "security benefits" of AWS sigv4. I hope the authors consider a different authentication scheme so I can recommend G…
There is a few "very minimal" sigv4 implementations ...