couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Deibert <mark.deib...@gmail.com>
Subject Re: Storage limitations?
Date Sun, 10 Nov 2013 21:17:12 GMT
So Couch will not handle lots (I hope many thousands eventually) of 3MB
photo attachments? This really stinks. So now I need to bring back a PHP
server script to support my Couchapp?


On Sun, Nov 10, 2013 at 4:10 PM, Mark Deibert <mark.deibert@gmail.com>wrote:

> Each comment is normally a very small amount of information, and id,
> userName, a date and a small text field. Probably no more than a short
> sentence on average. Why do I need to go through the trouble of creating
> new comment docs for each? This totally complicates the comment read code
> (there will 1000 reads to every 1 write, at least) both in the UI and the
> db for no reason.
>
>
> On Sun, Nov 10, 2013 at 1:34 PM, Jens Alfke <jens@couchbase.com> wrote:
>
>>
>> On Nov 9, 2013, at 11:47 AM, Robert Newson <rnewson@apache.org<mailto:
>> rnewson@apache.org>> wrote:
>>
>> attachments are different to documents. They're stored as a series of
>> binary chunks and so they can be streamed in and out, you can go large
>> with attachments.
>>
>> But on the other hand, all attachments will get copied during a database
>> compaction, so they slow down the process and require more free disk space.
>> If you have many gigabytes of attachments, you might consider storing them
>> externally and putting URL links in the documents.
>>
>> As for comments, just add new documents for each comment and use a
>> view (https://wiki.apache.org/couchdb/HTTP_view_API,
>> https://wiki.apache.org/couchdb/View_collation) to bring the article
>> and comment thread together. No need to update a document that way.
>>
>> Yup. The guide <guide.couchdb.org<http://guide.couchdb.org>> has a
>> chapter-long example of a blog application that shows how to do comments
>> this way.
>>
>> —Jens
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message