GraphCanon updated Sep 28, 2026 · GitHub synced Sep 28, 2026
31views this month
Decision brief
Distributed POSIX file system leveraging Redis and S3 for metadata and data blocks.
Good fit when
- Require low-latency access to large-scale data sets with object storage backing, such as S3
- Need a POSIX-compliant filesystem interface within cloud-native environments utilizing Redis
Avoid when
- Seeking a file system solution without the need for a separate metadata management tier like Redis
- Environment lacks suitable object storage compatible with JuiceFS or needs lower-latency metadata operations
Observed Jul 16, 2026 · Source: enrich:decision_facts
Verify the decision
Maintenance and security
Full trust report- Maintenance
- Very active (0d since push)
- As of Sep 28, 2026
- Provenance
- Not a fork · Organization account
- As of Sep 28, 2026
- Security (OSV)
- 33 low (33 low)
- As of Jul 11, 2026
Public GitHub metadata and optional OSV scans. Signals, not a guarantee. Trust methodology.
Install
go get github.com/juicedata/juicefsSimilar tools
Same-category neighbours. No typed graph edges are catalogued for this tool yet.
Evidence and technical details
Sourced facts, taxonomy, compatibility claims, README excerpt, and machine-readable endpoints.
Overview
JuiceFS provides a distributed file system with support for large-scale data storage using Redis for metadata and object storages like S3 for data blocks.
Capability facts
- MCP server
- No MCP server detected
Source: repo_scan · Sep 28, 2026
- Languages
- go, javascript
Source: github.language+package.json · Sep 28, 2026
Categories
Tags
README
Getting Started Before you begin, make sure you have: 1. One supported metadata engine, see How to Set Up Metadata Engine 2. One supported Object Storage for storing data blocks, see Supported Object Storage 3. JuiceFS Client downloaded and installed Please refer to Quick Start G...
For agents
This page has a .md twin and JSON over the API.