JuiceFS file system consists of three parts:
As a file system, JuiceFS will process data and its corresponding metadata separately, the data will be stored in the object storage, and the metadata will be stored in the metadata engine.
In terms of data storage, JuiceFS supports almost all public cloud object storage services, as well as privatized object storage such as OpenStack Swift, Ceph, and MinIO.
In terms of metadata storage, JuiceFS adopts a multi-engine design, and currently supports Redis, MySQL/MariaDB, SQLite as metadata service engines, and will continue to implement more metadata engine. Welcome to Submit Issue to feedback your needs!
In terms of the implementation of file system interface:
Now, you can refer to Quick Start Guide to start using JuiceFS immediately!
You can also learn more about How JuiceFS stores files
：Code submit frequency
：React/respond to issue & PR etc.
：Well-balanced team members and collaboration
：Recent popularity of project
：Star counts, download counts etc.