manta VS garage

These posts always remind me of the [Manta Object Storage](https://www.tritondatacenter.com/triton/object-storage) project by Joyent. This project was basically a combination of object storage with the added ability to run arbitrary programs against your data in situ. The primary, and key, difference being that you kept the data in place and distributed the program to the data storage nodes (the opposite of most data processing as I understand it), I think of this as a superpowered version of using [pssh](https://linux.die.net/man/1/pssh) to grep logs across a datacenter. Yet another idea before its time. Luckily, Joyent [open sourced](https://github.com/TritonDataCenter/manta) the work, but the fact that it still hasn't caught on as "The Way" is telling.

Some of the projects I remember from the Joyent team were: dumping recordings of local mariokart games to manta and running analytics on the raw video to generate office kart racer stats, the bog standard dump all the logs and map/reduce/grep/count them, and I think there was one about running mdb postmortems on terabytes of core dumps.

Are you sure this offers the same S3 compatible API? It sure does look like it rolled its own API[1], which I guess is fine so long as you're entirely in the Triton ecosystem, but makes reusing existing software harder than necessary without that compatibility layer. And that's not even getting into this absolutely mess: https://github.com/TritonDataCenter/manta#repositories it reminds me of the "Microservices" video come to life

1: https://github.com/TritonDataCenter/manta/blob/master/docs/u...

This is great information, and we've had similar experiences.

I'm also looking forward to further testing LinuxCN (https://github.com/joyent/linux-live/tree/linuxcn) on Triton in the near future!

Are you running Manta (https://github.com/joyent/manta) for anything? If so, is that meeting you needs for object storage?

Joyent's Manta took this concept to the extreme.

Previous discussion here: https://news.ycombinator.com/item?id=5939340

Image manipulation example: https://www.joyent.com/blog/joyent-manta-storage-service-ima...

Manta repo an GitHub: https://github.com/joyent/manta

Take a look at GarageS3, it's a niceoption for "just an S3 server" for self hosting.

https://garagehq.deuxfleurs.fr/

I use it for self hosting.

Garage (https://garagehq.deuxfleurs.fr/) gets pretty close for object storage. It’s built with mixing high/low latency links and replication between multiple hosts. Unfortunately it’s not really built for end-users, but devs, so there’s no ui or anything like that.

> Theoretically they could swap with minio but last time we used it it was not a drop-in replacement yet.

Depends on whether AGPL v3 works for you or not (or whether you decide to pay them), I guess: https://min.io/pricing

I've actually been looking for more open alternatives, but haven't found much.

Zenko CloudServer seemed to be somewhat promising, but doesn't seem to be managed very actively: https://github.com/scality/cloudserver/issues/4986 (their Docker images on DockerHub were last updated 10 months ago, which is what the homepage links to; blog doesn't seem active since 2019, forums don't have much going on, despite some action on GitHub still)

There was also Garage, but that one is also AGPL v3: https://garagehq.deuxfleurs.fr/

The closest I got was discovering that SeaweedFS has an S3 compatible mode: https://github.com/seaweedfs/seaweedfs

Ah, you should check out Garage (https://garagehq.deuxfleurs.fr/) for a self-hosted, cluster-y API of S3

I'm a big fan of Garage[1], which is a dead-simple S3 drop-in that you can host on your own drives. It's designed for consumer hardware with shitty internet in-between nodes.

[1]:https://garagehq.deuxfleurs.fr/

One more thing we are also proud of: a bunch of our users is using the object storage Garage, this OSS project looks really promising, and we really cherish the OSS for this kind of unexpected combination.

- Another nice comment seen on HN « it seems to be very easy to run, not very IO intensive, and running fine on a single node with modest hardware with >2 billion log rows. It has a really cool dynamic schema feature too.» [9]

Fun fact: at least 4 users are using Garage[10] as the object storage, this OSS project looks really promising and made the HN front page a few months ago[11], we really cherish the OSS for this kind of unexpected combination.

Any feedback positive/negative always greatly appreciated here!

[0] Quickwit repo: https://github.com/quickwit-oss/quickwit

[1] Searching the web under 1000$/month: https://news.ycombinator.com/item?id=27074481

[2] Chitchat gossip library: https://github.com/quickwit-oss/chitchat

[3] Columnar format: https://github.com/quickwit-oss/tantivy/tree/main/columnar

[4] Tantivy library: https://github.com/quickwit-oss/tantivy/

[5] Whichlang library: https://github.com/quickwit-oss/whichlang

[6] GitHub Archive demo in terminal: https://www.youtube.com/watch?v=SNq3bARRlDI

[7] Indexing performance: https://twitter.com/fulmicoton/status/1638016949459488768

[8] https://twitter.com/arnonrgo/status/1645429632303235073?s=20

[9] https://news.ycombinator.com/item?id=35742544

[10] Garage object storage: https://garagehq.deuxfleurs.fr/

[11] https://news.ycombinator.com/item?id=33853539

On the technical side, garage (https://garagehq.deuxfleurs.fr/) does multi master replication by default, so is probably better for this use case. Still with S3 API.

You are looking for garage.