@@ -163,20 +163,20 @@ For files on your file system, storing the files in a MongoDB database
163
163
through GridFS provides advantages in a number of situations:
164
164
165
165
- If your file system limits the number of files in a directory, you can
166
- use GridFS to store as many files as needed in a directory .
166
+ use GridFS to store as many files as needed.
167
167
168
168
- When you want to store file metadata (such as description, download
169
- count, and MD5 hash) together with the file itself. GridFS stores file
170
- metadata in the same bucket as the file's content.
169
+ count, and MD5 hash) together with the file itself. Storing the file
170
+ data and metadata is important in many scenarios and supported by
171
+ GridFS.
171
172
172
- - When you want to keep your files and metadata automatically backed up .
173
- If you set up replication, MongoDB makes automatic backups of your
174
- files and metadata .
173
+ - When you want to keep your files and metadata automatically synced .
174
+ If you set up replication, MongoDB replicates both the files and their
175
+ metadata so things won't get out of sync .
175
176
176
177
- When you want to access information from random sections of large
177
178
files without having to load whole files into memory. GridFS lets you
178
- access sections of files without having to read the entire file, for
179
- example skipping into the middle of a video.
179
+ access sections of files without having to read the entire file.
180
180
181
181
Do not use GridFS if a file is under the 16 MB limit and you need to
182
182
update the file atomically. Instead, consider either:
0 commit comments