Why is storing files in a database a bad idea?
- Is storing files in a database a bad idea?
- Should we store files in database?
- Why is storing images in database bad?
- Should I store files in the database or file system?
Is storing files in a database a bad idea?
Also, keep in mind that Web servers are cheap and you can easily add more to balance the load, whereas the database is the most expensive and hardest to scale part of a web architecture usually. There are some opposite examples (e.g., Microsoft Sharepoint), but usually, storing files in the database is not a good idea.
Should we store files in database?
Then why store files in DB ? DB provides ACID compliance(Atomicity, Consistency, Isolation, Durability) for each row. DB provides data integrity between the file and its metadata. Database Security is available by default.
Why is storing images in database bad?
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.
Should I store files in the database or file system?
Saving the files and downloading them in the file system is much simpler than database since a simple Save as function will help you out. Downloading can be done by addressing an URL with the location of the saved file.
Related Questions
-
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago