database - Storing Images in DB - Yea or Nay? -



database - Storing Images in DB - Yea or Nay? -

so i'm using app stores images heavily in db. what's outlook on this? i'm more of type store location in filesystem, store straight in db.

what think pros/cons?

i'm in charge of applications manage many tb of images. we've found storing file paths in database best.

there couple of issues:

database storage more expensive file scheme storage you can super-accelerate file scheme access standard off shelf products for example, many web servers utilize operating system's sendfile() scheme phone call asynchronously send file straight file scheme network interface. images stored in database don't benefit optimization. things web servers, etc, need no special coding or processing access images in file system databases win out transactional integrity between image , metadata important. it more complex manage integrity between db metadata , file scheme data it hard (within context of web application) guarantee info has been flushed disk on filesystem

database image theory storage blob

Comments

Popular posts from this blog

php - Android app custom user registration and login with cookie using facebook sdk -

django - Access session in user model .save() -

php - .htaccess Multiple Rewrite Rules / Prioritizing -