Enterprise DNA
O Open Source Observability medium

JuiceFS

by Community

JuiceFS is a distributed POSIX file system built on top of Redis and S3.

J

OSS

JuiceFS

Added 1 June 2026

#bigdata #cloud-native #distributed-systems #filesystem #go #golang #hdfs #object-storage

Overview

JuiceFS is a distributed POSIX file system that layers Redis for metadata and S3 for object storage. It exposes a standard file system interface across multiple machines, allowing applications to read and write files as if accessing a local drive while data persists in cloud storage.

Best for

Best for
Teams running distributed workloads on Kubernetes who need shared, cloud-backed storage without rewriting applications

Use cases

  • Sharing file storage across containerized workloads in Kubernetes
  • Scaling training datasets for machine learning pipelines
  • Building distributed caches backed by S3

Notes

JuiceFS is a distributed POSIX file system that layers Redis for metadata and S3 for object storage. It exposes a standard file system interface across multiple machines, allowing applications to read and write files as if accessing a local drive while data persists in cloud storage.

13,645 stars on GitHub. Last updated 2026-06-01. Licensed Apache-2.0.

Use cases

  • Sharing file storage across containerized workloads in Kubernetes
  • Scaling training datasets for machine learning pipelines
  • Building distributed caches backed by S3

Pros

  • POSIX-compatible interface reduces application refactoring
  • Decouples metadata (Redis) from object storage (S3) for independent scaling
  • Open source with active community (13k+ stars)

Cons

  • Requires operational overhead managing Redis cluster for metadata
  • Performance depends on Redis latency for every metadata operation
  • S3 egress costs accumulate quickly at scale

Indexed from awesome-llmops and enriched against its public facts.

Pros

  • POSIX-compatible interface reduces application refactoring
  • Decouples metadata (Redis) from object storage (S3) for independent scaling
  • Open source with active community (13k+ stars)

Cons

  • Requires operational overhead managing Redis cluster for metadata
  • Performance depends on Redis latency for every metadata operation
  • S3 egress costs accumulate quickly at scale