Why is storing images in database bad?

Question

Disadvantages of Storing BLOB Data in the Database Retrieving an image from a database incurs significant overhead compared to using the file system. Disk storage on database SANs is typically more expensive than storage on disks used in Web server farms. 7 окт. 2021 г.

Why is it bad to store images in a database?

The problem with storing only filepaths to images in a database is that the database's integrity can no longer be forced. If the actual image pointed to by the filepath becomes unavailable, the database unwittingly has an integrity error.

Is it a good idea to store images in a database?

As a general rule, it's a bad idea to store images in a database. This is due to the large amount of space they take up, which can affect database read performance and will greatly increases the size of your backups, making them both take longer and cost more to store.

Is it bad practice to store images in MySQL?

Images can get quite large, greater than 1MB. And so storing images in a database can potentially put unnecessary load on your database and the network between your database and your web server if they're on different hosts.

Is relational database good for image storage?

A relational database table can be used as a cloud object store. Customers who choose this option typically do so to capture images via the app and keep them along with the data in the same repository (convenient for backup and data management).

Expert · Answer