From 4deb66fd0e87fb2a000d7fa1edda01e029ef6103 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Tue, 29 Dec 2020 14:10:36 -0800 Subject: [PATCH] Updated Super Large Directories (markdown) --- Super-Large-Directories.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Super-Large-Directories.md b/Super-Large-Directories.md index d0f6674..252ee49 100644 --- a/Super-Large-Directories.md +++ b/Super-Large-Directories.md @@ -1,6 +1,6 @@ # Why need a super large directory? -This is actually a common case. For example, entity ids, such as user name, id, IP address, URLs, or UUID can be used as sub directory names. And under the sub directory, more unstructured data can be colocated together, such as user avatar, access logs, URL text, images, audio, video, etc. +This is actually a common case. For example, entity ids, such as user name, id, IP address, URLs, or UUID can be used as sub directory names. And under the sub directory, more unstructured data can be colocated together, such as user avatar, uploaded files, access logs, URL text, images, audio, video, etc. If using a separate lookup to translate the entity id to file id, and use file id to access data, this would give up all the convenience from a file system.