I’m adding some functionality to my site so that users can upload their own profile pictures, so I was wondering about whether to store them in the database as a BLOB, or put them in the file system.
I found a question similar to this here: Storing images in DB: Yea or Nay, but the answers given were geared more towards people expecting many many thousands or even millions of images, whereas I’m more concerned about small images (JPEGs up to maybe 150×150 pixels), and small numbers of them: perhaps up to one or two thousand.
What are the feelings about DB BLOB vs Filesystem for this scenario? How do clients go with caching images from the DB vs from the filesystem?
If BLOBs stored in the DB are the way to go – is there anything I should know about where to store them? Since I imagine that a majority of my users won’t be uploading a picture, should I create a user_pics table to (outer) join to the regular users table when needed?
Edit: I’m reopening this question, because it’s not a duplicate of those two you linked to. This question is specifically about the pros/cons of using a DB or FS for a SMALL number of images. As I said above, the other question is targeted towards people who need to store thousands upon thousands of large images.
To answer parts of your question:
For a database: Have a last_modified field in your database. Use the Last-Modified HTTP header so the client’s browser can cache properly. Be sure to send the appropriate responses when the browser requests for an image ‘if newer’ (can’t recall what it’s called; some HTTP request header).
For a filesystem: Do the same thing, but with the file’s modified time.
I would put the BLOB and related metadata in its own table, with some kind of relation between it and your user table. Doing this will make it easier to optimize the table storage method for your data, makes things tidier, and leaves room for expandability (e.g. a general ‘files’ table).