Davidson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 16, 2005 4:46 PM
To: jug-discussion@tucson-jug.org
Subject: Re: [jug-discussion] storing blobs on file system or in db
Andrew Huntwork wrote:
I'm writing this web app that allows users to upload documents, such
as word docs, images, etc
We started using a shared file system so we could easily invalidate the file
cache, but this came later.
-Original Message-
From: Randolph Kahle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 16, 2005 3:28 PM
To: jug-discussion@tucson-jug.org
Subject: Re: [jug-discussion] storing
:39 AM
To: 'jug-discussion@tucson-jug.org'
Subject: RE: [jug-discussion] storing blobs on file system or in db
We did both. We stored the file in the DB. Then when the file is retrieved
from the db, we write the file to the filesystem. The app would check for
the file on the file system first
The answer is partially dependent on your db, but if you want a rule of
thumb, then I suggest the fs. Some dbs really don't perform well when
moving blobs in and out of the DB.
Also, you need to fine tune your db and where you place the tables that
will hold the blob to minimize IO
Interesting question.
You could consider a shared file system.
I hesitate recommending that documents be stored in a database. You
don't need the transactional capabilities (correct?), and a RDMBS is
not really a great blob storage device (yes, they can do it, but I
don't reach for an RDBMS to
it looks like the clear consensus is file system. that's what 2 of my
co-workers said before i asked here, but now i actually basically
believe them.
I still have my doubts though...if someone has done this the db way and
actually seen real scalability problems, i'd love to hear about it.
-Original Message-
From: Andrew Huntwork [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 16, 2005 4:40 PM
To: jug-discussion@tucson-jug.org
Subject: Re: [jug-discussion] storing blobs on file system or in db
it looks like the clear consensus is file system. that's what 2 of my
co-workers said
Andrew Huntwork wrote:
I'm writing this web app that allows users to upload documents, such
as word docs, images, etc, and then to download those documents again
on request. the documents are not searched, interpretted, processed,
version controlled, or anything else. just upload and
I have, but then again I was using a @!#$!$ MS DBS at the time ;)
On Wed, 16 Mar 2005, Andrew Huntwork wrote:
it looks like the clear consensus is file system. that's what 2 of my
co-workers said before i asked here, but now i actually basically
believe them.
I still have my doubts
Taking into account all the responses I've seen so far (down to J. D.
Mitchell) there is
relatively little consideration being given to the transactional issues.
I suggest that before you settle on a solution where performance is the
priority
you need to examine the issue of "What is the
10 matches
Mail list logo
