Is it good to save images to a database or filesystem?

Possible duplicate:
Saving images to DB - Yea or Nay?

What do you recommend for storing images in: -

  • File system or
  • Database

This is a conceptual question that I want to conclude which approach is best in different projects.

Note: please confirm which approach is better.

0


a source to share


3 answers


Which is best depends on your situation (of course). Storing them in the database means the system is pretty much completely portable. Everything is closely connected and "travels" together.



The downside is that everything is tightly coupled and you have to get into the database to get the image. This includes running any code required to connect to the image information processing database. This is a lot of overhead.

+1


a source


There is no need to store images in your database because you will never search for them based on the data itself. Instead, you should store them on the file system and store the file paths in the database. Once you've put the data on your hard drive, you can access it directly for other programs, including backups. Smaller SQL is easier to maintain.



0


a source


No, no more, or really never. It is used to be acceptable if you needed to access something like a user image from any application and there was no real way to store it on a global server. But right now, with alternatives like the Amazon Cloud API for storing images, they no longer need to store them in a database, you use the Amazon Cloud as your database.

0


a source







All Articles