Is it a good idea to store hundreds of millions small images to a key/value store or other nosql database?


HOME ยป Databases

I am developing a web system to handle a very large set of small
images, about 100 millions images of 50kb ~ 200kb, working on
ReiserFS.


For now, it is very difficult
to backup and sync
those large number of small files.

/>

My question is that if it a good idea to store these small images
to a key/value store or other nosql database such as GridFS
(Mongodb)
, Tokyo Tyrant, Voldemort to
gain more performance and bring better backup support?

I am developing a web system to handle a very large set of small
images, about 100 millions images of 50kb ~ 200kb, working on
ReiserFS.


For now, it is very difficult
to backup and sync
those large number of small files.

/>

My question is that if it a good idea to store these small images
to a key/value store or other nosql database such as GridFS
(Mongodb)
, Tokyo Tyrant, Voldemort to
gain more performance and bring better backup support?

Databases

Some discussions in Stackoverflow say that storing the picture in
DB is a bad idea (a because overtime, the number of images get large
& may lead to app crash). So, either


a. the image can
be stored in the iPhone itself & only its location can be stored
in the DB
Potential Issue: The image might get removed
(outside of the app) & the app might not be able to load them the
next time


b. the image can be shrunk to a small size (say,
100*100 pixels) and stored in the DB
Potential Issue:
will size be an issue if the image is shrunk to just
100x100pixels?


c. Doing both (a) & (b). So, small ver

Mobile Programming

I need to store millions of small images 0,1kb-8Mb. I heard about
gridfs but I can read in docu "For documents in a MongoDB collection,
you should always use GridFS for storing files larger than 16 MB.". So
it is not good solution for many small files ? I am looking for the
fastest way to store images (and other binary files)

Databases

I know you will say there are several duplicates for this question.
I've read most of them. But I need an answer to the specific case I'm
presenting.


I'm planning to store millions of small jpg
images (about 3kb) in a Firebird database.

/>

Assumptions:
- The table that will contain these images will
not contain any other information but its key;
- It is not a web
application;
- The images will never be updated;
- In most of
the cases, the database will never grow to more than one digit
GB;
- The server must be easy to be maintained, as there will be no
DBA to take care of it.


Is

Programming Languages
Hello,
Im currently developing social website which means that Im
going to use user images/avatars, photo albums etc. Is it a good idea
to store all those images in MySQL database instead of using
individual user folders?
Thank You )))
Development
I am trying to develop an image gallery with categories using php and
intend to store these images in an ODBC database. Since I will be
having many categories is it advisable to use a database. I am
thinking images might slow down the database, etc.
PHP

- Technology - Languages
+ Webmasters
+ Development
+ Development Tools
+ Internet
+ Mobile Programming
+ Linux
+ Unix
+ Apple
+ Ubuntu
+ Mobile & Tablets
+ Databases
+ Android
+ Network & Servers
+ Operating Systems
+ Coding
+ Design Software
+ Web Development
+ Game Development
+ Access
+ Excel
+ Web Design
+ Web Hosting
+ Web Site Reviews
+ Domain Name
+ Information Security
+ Software
+ Computers
+ Electronics
+ Hardware
+ Windows
+ PHP
+ ASP/ASP.Net
+ C/C++/C#
+ VB/VB.Net
+ JAVA
+ Javascript
+ Programming
Privacy Policy - Copyrights Notice - Feedback - Report Violation 2018 © BigHow