Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of thadguidry@gmail.com designates
 209.85.132.191 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20090626093451.GA11503@uk.tiscali.com>
Message-ID: <0016e644cef637ee21046d41cf5a@google.com>
Date: Fri, 26 Jun 2009 15:15:23 +0000
Subject: Re: Re: 'Grouping' documents so that a set of documents is passed to
	the view function
From: thadguidry@gmail.com
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0016e644cef637ee0b046d41cf57

--0016e644cef637ee0b046d41cf57
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

Brian,

Could a better approach be to use an ETL tool such as Jasper or Pentaho to  
perform the analysis and either use them to display or load another CouchDB  
or MySQL instance for viewing the data ? I would instead opt to perform  
analysis with a Business Intelligence suite, unless the reporting solution  
needs are fairly basic, since he mentioned growth would be a factor. Growth  
could be accounted for within a Data Warehouse, separate from CouchDB, or  
kept inside it. Something to consider. But my background is in Enterprise  
architectures & scaling.

-Thad

On Jun 26, 2009 4:34am, Brian Candler <B.Candler@pobox.com> wrote:
> On Fri, Jun 26, 2009 at 05:13:18PM +0800, hhsuper wrote:

> > by the way, we select to use couchdb as a part our current application,

> > because that part of data is huge and with everyday got growth, we need

> > do some analysis on these data and then give the result back to the

> > user( though our website), maybe i need consider another solution:

> > analysis still with couchdb view, but not query that directly to the

> > web, we maybe give a cron job sync the analysis(couchdb view) data to a

> > mysql table and then use the result data in mysql table to feed the

> > webpage, that is easy to paging and sorting at mysql level, this is a

> > rough thought only.


> Yep, we seem to have had the same idea. Or maybe it may make sense to

> perform the analysis or partial analysis when exporting, and stick the

> summarised data into another couchdb database which is searched via the  
> web.


--0016e644cef637ee0b046d41cf57--