问题
I’m writing an upload function in .NET for presentation images on user profiles. I’m choosing between two different ways of doing it, and would like to ask on advice and opinions as to the pros and cons.
Store the images directly on the file system
Store the images in the database
So far I’ve been mostly pro the first option – naming the images after the usernames, as each user can only have one presentation image. Then I do a check in the designated path if the user has an image, if not display a default “no image”-image.
Another thing I like about this is that it saves space in the DB – the DB will be pretty heavy without the extra binary load.
I’m sure there are other aspects that I’ve not thought about, so I’d like to hear your opinions on this. If anyone’s got a radically different solution to the problem, please share that as well!
回答1:
Your question has been answered before on StackOverflow:
Store pictures as files or in the database for a web app
Including many other duplicate questions!
回答2:
In general, it is better to store files on the file system. File systems are already tuned for storing files. However, this does have its drawbacks, particularly in terms of management, backup, restore and it is somewhat of a flimsy tie between a varchar file path field in the database and a file in the file system. What database system are you using? I think if you are using SQL Server 2008, that the new FileStream type gives a very good method for storing files in that database.
Edit: Note I'm really talking about more generally about storing files in the database. There is some extra complexity involved in trying to store images you intend to display on HTML pages in the database.
回答3:
Filesystem is good, but is not practical with more than 3000 image per folder. It's better to write automatic folder creation for every 3000 images blocks.
回答4:
data redundency and inconsistency difficulty in accessing of data data isolation integrity constraints atomicity problem concurrent access and anomalies (updation security problem
回答5:
For fixed (non changing) content such as photos, videos, etc. filesystems won't be able to scale especially if you have lots of files in a directory and performance will really suffer. A better option is to use object storage technology which stores the image as an object and puts the associated metadata in the database automatically.
回答6:
How about storing doc, pdf, xls, jpg files? Which one recommended?
I am going to work on a document management system which might store 10000 files but the problem is I am very worry about virus spreading if we use file system technique.
来源：https://stackoverflow.com/questions/585224/user-images-database-vs-filesystem-storage