fun consideration: any file system can act as a key-value store any key-value store can act as a content addressable data store through with limitations like

fun consideration: any file system can act as a key-value store any key-value store can act as a content addressable data store through with limitations like fundamental constraints not being enforced, performance problems and potential unexpected problems (like the number of files per folder) for above reason and given that content addressable storage is a poster child for fast(1) distributed reliable solutions (1: At least in "single entity owned backend database case") I would never recommend using the file system for it outside of prototyping (and system internal use cases like docker storage).