juicefs
VFSForGit
Our great sponsors
juicefs | VFSForGit | |
---|---|---|
42 | 23 | |
9,675 | 5,919 | |
4.1% | 0.4% | |
9.7 | 4.7 | |
3 days ago | 14 days ago | |
Go | C# | |
Apache License 2.0 | MIT License |
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
-
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.
-
Gcsfuse: A user-space file system for interacting with Google Cloud Storage
If you really expect a file system experience over GCS, please try JuiceFS [1], which scales to 10 billions of files pretty well with TiKV or FoundationDB as meta engine.
PS, I'm founder of JuiceFS.
The architecture image shows GCS and others, so I suspect it does.
-
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.
-
Open source cloud file system. Posix, HDFS and S3 compatible
Atomic file/directory renames/moves is the fundamental feature of JuiceFS, which makes it truely a file system rather than a proxy to S3, please check the docs for all the compatibility details [1].
- An open-source distributed object storage service
-
POSIX Compatibility Comparison among four file system on the cloud
From Juicedata/JuiceFS ! (0ᴗ0✿)
VFSForGit
-
Serving a Website from a Git Repo Without Cloning It
Congratulations! That means you basically figured out how the clone procedure works and found a way to do so just in a partial way (also in an unsafe way). But it is a cool idea, nonetheless.
Also check out the Scalar [1] project and its predecessor, GVFS [2], both from Microsoft to manage their monorepo via a VFS layer.
-
We Put Half a Million Files in One Git Repository, Here's What We Learned (2022)
VFS for Git is still Open Source: https://github.com/microsoft/VFSForGit
Microsoft's blog posts have indicated a move to use something as close to off-the-shelf git as possible, though. They say they've stopped using VFS much and are instead more often relying on sparse checkouts. They've upstreamed a lot of patches into git itself, and maintain their own git fork but the fork distance is generally shrinking as those patches upstream.
-
Why SQLite Does Not Use Git
https://github.com/microsoft/VFSForGit
better than it used to, with the caveat that git in particular is not and has never claimed to be good at versioning blobs.
-
🐂 🌾 Oxen.ai - Blazing Fast Unstructured Data Version Control, built in Rust
Oh dear you're not going to like this.
-
He is very conservative...
It’s virtualised file system: https://github.com/microsoft/VFSForGit, only downloads what you actually use. Same thing in every large company, but different implementations.
-
FYI: LLVM-project repo has exceeded GitHub upload size limit
This is where something like VFSForGit[0] helps out. Instead of cloning the entire repo, it creates a virtual file system and fetches objects on demand. MSFT uses it internally for the Windows source tree (which now exceeds 300GB).
-
Created a Small Program To Display Upcoming Assignments On My Desktop
There's also a performance consideration. Not excluding /bin/ or /obj/ folders means dependencies are being tracked as well, and sometimes dependencies themselves are bigger than the program's source code itself. This is commonly the case with node projects, as the node_modules folder can balloon to hundreds of megabytes. They should never be tracked in git due to the nature of how git's internal database works. For e.g. if you delete a dependency because it's no longer needed, you can never fully reclaim that disk space (at least for the master branch) as git will need to keep the binary data stored in its internal tracking database because a previous commit in the master branch has captured the data. As you make more branches, git needs to store the data required to reconstruct your repo to a different state when you switch branches. When a branch has changes measured in the kilobytes, check out is very manageable, but when the differences balloon to many MBs due to the presence of heavy binary files, then checkout between different branches/commits can get very slow. Though, this happens anyway when source code data eventually reaches a certain threshold, beyond the hundreds of megabytes, it's made unnecessarily worse by including any binary files. It's one of the reasons Microsoft created VFS for git: https://github.com/microsoft/VFSForGit.
- Meta releases Sapling, a new way of using source control
-
Software for managing config files
You mean like VFSforGit? Or the successor for that called Scalar? This has been a solved problem. Microsoft moved their entire Windows codebase to git. There have been a ton of huge improvements to performance as a result of that. And the above two plugins are easily better ways to deal with what you're referring to without resulting to dead tech.
-
WebKit Migrates from Subversion to GitHub
I was just looking at Microsoft's git VFS (https://github.com/microsoft/VFSForGit), which is deprecated and now points to Scalar (https://github.com/microsoft/scalar), which is also deprecated? What's Microsoft's story with git now? Is there still a virtual file system involved?
What are some alternatives?
cubefs - cloud-native file store
goofys - a high-performance, POSIX-ish Amazon S3 file system written in Go
s3-benchmark - Measure Amazon S3's performance from any location.
gcsfuse - A user-space file system for interacting with Google Cloud Storage
hdfs - A native go client for HDFS
Golang-PDF-to-Image-Converter - This project will help you to convert PDF file to IMAGE using golang.
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
scalar - Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer
redisraft - A Redis Module that make it possible to create a consistent Raft cluster from multiple Redis instances.
go-sanitize - :bathtub: Golang library of simple to use sanitation functions
JSON-to-Go - Translates JSON into a Go type in your browser instantly (original)
go-lock - go-lock is a lock library implementing read-write mutex and read-write trylock without starvation