SeaweedFS is a scalable distributed file system optimized for exabyte small files, supports FUSE, S3 API, Hadoop, k8s, replication, Cloud Drive, S3 gateway.

San Francisco
Joined March 2020
SeaweedFS retweeted
In PostgreSQL, a 1,000,000-row table starts at 152 MB in the heap. After the pgEdge ColdFront archiver runs, 958,056 of those rows sit as Parquet files in object storage and the hot heap is down to 6624 kB. The table name and the SQL stay the same. ColdFront is open source (PostgreSQL License) data tiering for PostgreSQL 16, 17, and 18. It moves older partitions to Apache Iceberg on S3 and keeps that data queryable and writable. In the new walkthrough, an UPDATE on an archived row lands directly in object storage, with no rehydration and no restore job. A lake-native table stores 0 bytes in Postgres and takes plain INSERT, UPDATE, and DELETE. Concurrent writers across two Postgres nodes with 0 conflicts, 0 Lakekeeper 409s, and 12 Iceberg snapshots for 12 writes. There's no narration and every step is explained on screen, so pause anywhere to read the SQL. The demos run on a local Docker stack with SeaweedFS standing in for a cloud bucket. Watch the walkthrough: 🎬 hubs.ly/Q04z8QhR0 ColdFront on GitHub: 🔗 hubs.ly/Q04z8QkL0 #postgres #postgresql #apacheiceberg #opensource #dataengineering #database #datalake #parquet #s3 #docker #pgedge #coldfront
1
3
105
SeaweedFS retweeted
Head to head SeaweedFS vs RustFS
1
1
2
219
It's, using celld and SeaweedFS for storage. And it's a live multiplayer reaction game: a light flashes at the same instant for everyone on the page, timed by a Durable Object's own alarm. First click wins.
1
92
SeaweedFS Table Buckets can tier each part independently, automatically based on data temperature. ⚡ Metadata → replicated SSD 📦 Parquet data → HDD 🧊 Cold data → erasure coding / cloud ⚡ Parquet footers → cached back on SSD seaweedfs.com/blog/volume-ti…
2
12
568
Why choose between Iceberg and Lance? You can analyze with Iceberg, and serve with Lance point lookups and vector search, with DuckDB joins them together. SeaweedFS can host both table formats on the same object store, with built-in catalogs for each. seaweedfs.com/blog/iceberg-l…
1
6
382
SeaweedFS retweeted
~@SeaweedFS has been absolutely vital to my development work on arkfile.net. Self-hosting assumes the use of `local-seaweedfs` backend by default. You can set up two buckets & replicate from primary to secondary as well. See: github.com/arkfile/Arkfile
1
2
119
SeaweedFS + Cloud ⚡ reads at local-disk latency ☁️ writes synced back to Cloud With SeaweedFS, cloud S3 can remain the durable source of truth while SeaweedFS provides a nearby cache. WALGit is a great example of this. seaweedfs.com/blog/walgit-se…
13
850
Git on S3 is hot. Running it on SeaweedFS for faster operations and no storage or access fees would be perfect. xitter.cf/i/trending/20917221439…

4
301
for everyone glazing s3 right now, please go watch this talk from fmr Docker CTO during @CloudNativeFdn last yr titled “Object Storage is All You Need” this is what got me objectstore-pilled back in 2024 youtu.be/ei0wwTy6_G4?si=72M7…
17
113
11,979
SeaweedFS retweeted
Somebody shared a design idea(forgot who), Isometric Map of codebase. Tried with seaweedfs codebase. Looks pleasing to the eyes. I think if I continue to iterate over it for more, can be made useful for understanding high level codebase and then drilling down. Need more visualization for drill down. What do you think? Artifact link in the comment.
2
1
3
261