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 <[email protected]> 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.
