MongoDB Guide (translated) (16)-developer zone-when to use gridfs

When to use GridFS

• A large number of files. GirdFS performs better than many file systems when processing large (several thousand) files.
• Files uploaded by the user. When a user uploads a file, you may have a large number of files and want to copy them and back up them. GridFS is an ideal way to save them, so you can manage these files as you want to manage common data. You can also use the keyword user to wait for the upload time to be directly queried in the data warehouse without passing through the indirect layer.
• Files that are frequently changed. If you have some files that will change frequently-it makes sense to store them in GridFS, so that you can modify them in one place, and then all clients will obtain these updates. It is better than storing it in the directory tree, so that you do not need to deploy applications to update files.

When to disable GridFS

• A small number of unchanged files. If you have small files (js, css, and images) on some websites, it may be easier to directly use the file system.
• If you need to perform atomic update on binary objects, and the object size is limited by the Mongodb version you use (the 1.8 version is 16 MB ), you can save the object in a single document. This can be done using the BSON binary type. Find detailed information about this type in your driver documentation.