Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Garage: An open-source distributed object storage service

garagehq.deuxfleurs.fr

Post reply on HN
Print view View original

11–20 of 81 posts

Re: Garage: An open-source distributed object storage service

#11

Post by tyingq »

ilyt wrote: post #7
throwawayk8s wrote: post #5

Is there any OSS implementation that is not AGPL?

Why would that matter? Apps using its api don't need to be AGPL

For some places, the in-house legal department makes it very difficult to use anything AGPL even if you assure them you're only using the api.

Re: Garage: An open-source distributed object storage service

#14

Post by seized »

Just finished installing it on my OpenIndiana NAS to replace Minio.

Biggest difference so far is that Minio is just files on disk, Garage chunks all files and has a metadata db.

Minios listing operations were horribly slow, still have to see if Garage resolves that.

Re: Garage: An open-source distributed object storage service

#16

Post by wvh »

ollybee wrote: post #3

It looks similar to minio, which as also an AGPL single binary that implements the S3 API. However Minio is written in Go and Garage is in Rust. I'd love to see a detailed comparison.

We're running Ceph with Rook and Minio in Kubernetes. I'm evaluating Garage as an alternative for some purposes such as application instance static files for Python or Javascript applications to avoid block volumes in deployments. Garage has a simpler high availability distribution story than Minio's erasure coding striping, but it works well for applications that don't require sub-second writes. It can do high availability with only three nodes versus four for Minio, which works well for smaller setups. It can also serve static websites straight from a bucket, which would work well for static sites like those made with static site generators.

Ceph has an S3 API gateway, but it's a more wholesome solution better suited for larger setups compared to Minio and Garage.

Re: Garage: An open-source distributed object storage service

#17

Post by remram »

Terretta wrote: post #4
ollybee wrote: post #3

It looks similar to minio, which as also an AGPL single binary that implements the S3 API. However Minio is written in Go and Garage is in Rust. I'd love to see a detailed comparison.

Garage design goals and non-goals: https://garagehq.deuxfleurs.fr/documentation/design/goals/ Seaweed design goals / features: https://github.com/seaweedfs/seaweedfs MinIO: https://min.io/docs/minio/linux/operations/concepts.html Note Garage list of non goals specify priority features of Seaweed or MinIO, for example erasure coding.

Reading that only makes Minio and Garage seem more similar. They are both single-binary, clustered, S3-compatible file storage solutions. They are both meant for self-hosting on consumer-grade hard drives, provide redundancy to deal with drive or node failures, and don't aim to implement the entire AWS S3 API surface.

Re: Garage: An open-source distributed object storage service

#18

Post by remram »

throwawayk8s wrote: post #10
ilyt wrote: post #7

Earlier quoted context omitted.

Why would that matter? Apps using its api don't need to be AGPL

We would like to self host and our legal team forbids us from using AGPL stuff.

Sounds like a problem created entirely by your legal team, not software or licenses.

Re: Garage: An open-source distributed object storage service

#19

Post by tomrod »

remram wrote: post #18
throwawayk8s wrote: post #10

Earlier quoted context omitted.

We would like to self host and our legal team forbids us from using AGPL stuff.

Sounds like a problem created entirely by your legal team, not software or licenses.

Working with legal is advisable instead of ignoring it.

Re: Garage: An open-source distributed object storage service

#20

Post by vlovich123 »

ilyt wrote: post #7
throwawayk8s wrote: post #5

Is there any OSS implementation that is not AGPL?

Why would that matter? Apps using its api don't need to be AGPL

This doesn’t seem accurate. Isn’t AGPL viral across RPC boundaries requiring open sourcing not just the service but all supporting code for that service?
Post reply on HN