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 download. i
wonder if there's
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.
I forgot to mention this in my previous post, but I did a lot
benchmarking around this a few years ago and did several consulting gigs
where people needed to rip out the blob in db infrastructure they had
built because it was performing like a dog (a bad dog, not a good dog).
landon
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
Andrew == Andrew Huntwork [EMAIL PROTECTED] writes:
[...]
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
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