View Single Post
  #3  
Old 5th September 2008, 18:14
bagpiperdude90 bagpiperdude90 is offline
Member
 
Join Date: Mar 2007
Posts: 34
Thanks: 4
Thanked 22 Times in 5 Posts
Default

Quote:
Originally Posted by Ben View Post
Well the biggest problem I see here is dumping the DB, as it will get very huge the more photos you will need to store.
Another thing are thumbnails, do you plan to use such? If so you will have to store photo + thumb, so calculated with low values of 150kb per foto (which is very small) and 50kb per thumbnail will mean about 20GB ot tablespace just because of storing fotos there. I don't want to know how much time it takes restoring the DB in case of a crash.

I'd suggest storing the images + generated thumbs on a hdd. This will also give you the flexibility to e.g. move the images to a completely different server once as there you will need storage more than a fast cpu.

Regarding the direct access, it's not a big deal preventing the webserver to have access to the imagefolder. Instead code a script serving the pictures.


Fetching images is not a big deal for a DB as a DB is used to do complex queries. It's like using a sledge-hammer to crack a nut.
Well, I'm glad I decided to switch to file-based, then.

I was worried about a few things, namely the backing up the database, and what would happen if the database crashed - how long would it take to restore it, etc.

Thanks for the input!
Reply With Quote