HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
chrislusf
seaweedfs
Go2015–2022
chrislusf / seaweedfs

seaweedfs

SeaweedFS is a fast distributed storage system for blobs, objects, files, and data lake, for billions of files! Blob store has O(1) disk seek, cloud tiering. Filer supports Cloud Drive, xDC replication, Kubernetes, POSIX FUSE mount, S3 API, S3 Gateway, Hadoop, WebDAV, encryption, Erasure Coding. Enterprise version is at seaweedfs.com.

21Distinct people
44Mentions
0Explicit recommenders
45GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

SeaweedFS is a fast distributed storage system for blobs, objects, files, and data lake, for billions of files! Blob store has O(1) disk seek, cloud tiering. Filer supports Cloud Drive, xDC replication, Kubernetes, POSIX FUSE mount, S3 API, S3 Gateway, Hadoop, WebDAV, encryption, Erasure Coding. Enterprise version is at seaweedfs.com.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 2:19:09 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year44 dated mentions

Observed mentions: 2015-04-25 05:19:51 UTC to 2022-12-04 14:08:58 UTC.

051015202015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 5 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 18 mentions; 0 submissions, 18 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC321
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC413
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC954
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC18018
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC918

What Hacker News says

9 sources
chrislusf·Dec 30, 2020Submission

Use the distributed file system as a Key-Large-Value store

I am working on SeaweedFS, and developed a feature that should be interesting. Basically, it enhances a distributed key value store, such as Redis/Cassandra/HBase/MongoDB to a distributed key-large-value store, by storing large values as files to SeaweedFS. The smaller values can be optionally stored in the KV store directly, saving one network hop. Let me what you think. https://github.com/chrislusf/seaweedfs/wiki/Filer-as-a-Key-Large-Value-Store
2 points · Open discussion
So I have no idea what would work for you and am not in a position to make a solid recommendation.... buuuut this is the internet so I'll list some possibilities in order of perceived production worthiness: - Good ol' trusty NFS[0][1] (of course someone has to take an arrow to the knee and become an NFS admin essentially) - CephFS[2] via Rook Shared filesystem[3] - Swift[4] though it looks like a huge PITA to deploy outside of openstack, almost like it's hard on purpose - Dragonfly[5]? I remember think of it for containers but it's technically for random files too - SeaweedFS[6]? It's got a comparison section which is a good sign?? - Could you just... offload to some S3-like thing? [0]: https://kubernetesguide.com/kubernetes/nfs-volumes-in-kubern... [1]: https://www.padok.fr/en/blog/readwritemany-nfs-kubernetes [2]: https://docs.ceph.com/
Read the rest
In Mayastor: Lightning Fast Storage for Kubernetes
It depends on your project. I used Go since 2011 on multiple projects, two of them are http://github.com/chrislusf/seaweedfs and http://github.com/chrislusf/gleam. One is a distributed file system, the other is a distributed computation. * Refactoring is powerful ========== Nobody can design well upfront for a large project. Constant refactoring is need for large projects. Go is super good on this. * Generics is not ready yet. ========== The distributed computation project was re-written multiple times. I tried different approaches to address the generics problem. I even tried to make it work fairly well with LuaJIT, but still decide to change again due to the need to learn a different scripting language and losing the type checking.
In Ask HN: Go programming language is over ten years old. What do you think of it?
Whenever you introduce a new solution into a problem space that already has plenty of options, you are obligated to state why your (new) solution is needed in the first place, IMO. They did it well: > Most other distributed file systems seem more complicated than necessary. > SeaweedFS is meant to be fast and simple, in both setup and operation. If you do not understand how it works when you reach here, we've failed! Please raise an issue with any questions or update this file with clarifications. https://github.com/chrislusf/seaweedfs#compared-to-other-fil... However, since I never had to touch hdfs after installing it in the first place, I wonder what the difficulties in operation are, that they tried to overcome here?
In SeaweedFS – A simple and highly scalable distributed file system with S3 API

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.