juicefs
s3fs-fuse
juicefs | s3fs-fuse | |
---|---|---|
45 | 57 | |
9,881 | 8,122 | |
2.1% | 1.4% | |
9.8 | 8.8 | |
1 day ago | 10 days ago | |
Go | C++ | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
juicefs
-
JuiceFS 1.2 Beta 1: Gateway Upgrade, Enhanced Multi-User Permission Management
Feel free to download and try JuiceFS 1.2-beta1 here. If you have any questions, join JuiceFS discussions on GitHub and our community on Slack.
-
South Korea's No.1 Search Engine Chose JuiceFS over Alluxio for AI Storage
Support for Kerberos keytab files
-
5 Open Source tools written in Golang that you should know about
JuiceFS under the Apache License 2.0, is a high-performance POSIX file system optimized for cloud-native environments. It stores data in Object Storage (e.g., Amazon S3) and metadata in databases like Redis, MySQL, or TiKV. JuiceFS integrates massive cloud storage with big data, machine learning, and AI applications efficiently, akin to local storage. It features full POSIX and Hadoop compatibility, S3 interface, Kubernetes support, and shared file storage for numerous clients. Some cool features are - strong consistency, scalable performance, data encryption, global file locks, and compression with LZ4 or Zstandard.
-
How to Build a Ceph Cluster and Integrate with the JuiceFS File System
To improve the handling process of capacity overrun, the JuiceFS client supports deletion operations in the case of Ceph cluster fullness (see related code changes in JuiceFS Community Edition). Therefore, for newer client versions, there is no need to use set-full-ratio for temporary adjustments.
-
A Deep Dive into the Design of Directory Quotas in JuiceFS
If you have any questions or would like to learn more, feel free to join discussions about JuiceFS on GitHub and the JuiceFS community on Slack.
- JuiceFS 1.1 - Distributed File System written in Go
-
Gcsfuse: A user-space file system for interacting with Google Cloud Storage
The architecture image shows GCS and others, so I suspect it does.
https://github.com/juicedata/juicefs#architecture
-
Google Cloud Storage FUSE
See also: JuiceFS: https://juicefs.com/
Adds a DBMS or key-value store for metadata, making the filesystem much faster (POSIX, small overwrites don't have to replace a full object in the GCS/S3 backend).
Almost certainly a better solution if you want to turn your object storage into a mountable filesystem, with the (big) caveat that you can't access the files directly in the bucket (they are not stored transparently).
- Using S3 as shared storage
-
s3fs-fuse VS juicefs - a user suggested alternative
2 projects | 19 Feb 2023
JuiceFS can do the same thing as s3fs-fuse, but better. Because it supports robust data consistency and caching policies to improve performance.
s3fs-fuse
-
Is Posix Outdated?
The author needs to ask themselves: in this cloud technology stack, is there POSIX involved somewhere lower down, where I can't access it? The answer is, of course, "yes". The sort of cloud storage systems described all run on top of POSIX APIs. They provide convenience (cost efficiency is more debatable) compared to the POSIX alternative, but that's because they exist at an entirely different conceptual layer (hence the presence of POSIX anyway, just buried).
Your point about surfacing a POSIX that's actually there but hidden and thus visible to low-level Amazon employees building the S3 service which makes it invisible to S3 end customers is true but isn't the the point of the article. The author is saying there are motivations for a POSIX-like api visible also the end user.
So your explanation of stack looks like 2 layers: POSIX api <-- AWS S3 built on top of that
Author's essay is actually talking about 3 layers: POSIX <-- AWS S3 <-- POSIX
That's why the blog post has the following links to POSIX-on-top-of-S3-objects :
https://github.com/s3fs-fuse/s3fs-fuse
https://github.com/kahing/goofys
https://www.cuno.io/
- Gcsfuse: A user-space file system for interacting with Google Cloud Storage
-
R2 slow PUT file transfer
sudo apt install build-essential libfuse-dev fuse git clone https://github.com/s3fs-fuse/s3fs-fuse.git cd s3fs-fuse sudo apt install libfuse2 sudo apt install libcurl4-openssl-dev sudo apt install libxml2-dev ./autogen.sh ./configure make
- Cloud Backed SQLite
-
Podman and S3 Storage Driver (Audiobookshelf)
Don’t know actually. Here is project page.
- Uploading hundreds to thousands of files to S3
- Linux Client for R2
-
s3fs-fuse - allows to mount your s3/minio bucket link to your local directory
s3fs-fuse
-
AWS Announces Open Source Mountpoint for Amazon S3
How is this different than these other solutions?
https://github.com/kahing/goofys
https://github.com/s3fs-fuse/s3fs-fuse
-
Introducing Mountpoint for Amazon S3 - A file client that translates local file system API calls to S3 object API calls like GET and LIST.
I don’t get it. Why not just improve https://github.com/s3fs-fuse/s3fs-fuse
What are some alternatives?
cubefs - cloud-native file store
goofys - a high-performance, POSIX-ish Amazon S3 file system written in Go
rclone - "rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
s3-benchmark - Measure Amazon S3's performance from any location.
mountpoint-s3 - A simple, high-throughput file client for mounting an Amazon S3 bucket as a local file system.
gcsfuse - A user-space file system for interacting with Google Cloud Storage
jellyfin-webos - WebOS Client for Jellyfin
Golang-PDF-to-Image-Converter - This project will help you to convert PDF file to IMAGE using golang.
jellyfin-tizen - Jellyfin Samsung TV Client
hdfs - A native go client for HDFS
mediacms - MediaCMS is a modern, fully featured open source video and media CMS, written in Python/Django and React, featuring a REST API.