5,323
edits
File Systems: Difference between revisions
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
There are several common ways to store binary information: | |||
* Database or key-value store (e.g. PostgreSQL, SQLite) - Good for small files or a finite amount of files which fit within the confines of a database. | |||
* Object store (e.g. S3) - same as a key-value store but typically designed to scale lots of files across multiple HDDs and hosts. | |||
* File systems (e.g. EXT4) - good for files where certain operations benefit from a hierarchical data structure, e.g. list, delete. File systems typically come with metadata such as permissions and owners. | |||
* Block storage - you get raw disk access but need to layout your binary data manually and in fixed block sizes. | |||
==Standard File Systems== | ==Standard File Systems== | ||
| Line 22: | Line 26: | ||
* JuiceFS - creates a POSIX-compatable file storage using an S3 object storage and metadata database. | * JuiceFS - creates a POSIX-compatable file storage using an S3 object storage and metadata database. | ||
* Rook - deployment of Ceph using Kubernetes | * Rook - deployment of Ceph using Kubernetes | ||
==Databases== | |||
* PostgreSQL | |||
* MySQL | |||
* SQLite | |||