incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alon Keren <>
Subject Re: Options for Iterative Map Reduce
Date Thu, 13 Dec 2012 09:49:58 GMT
On 13 December 2012 01:07, nicholas a. evans <> wrote:

> Unfortunately, those TODOs and Caveats are part of what nix
> couch-incarnate for us. "input validation"; I made it crash several
> times (with invalid JSON) while I was testing it out. "limited
> error-handling" and "tests. Does this thing really work?";
> self-explanatory.  ;)  The crashing plus the lack of recent commits
> made me think it was more of a (damn fine) proof of concept or a beta
> release than a production hardened code base.

There's no fault in your logic there. I would have loved to make it more
production ready, but I simply couldn't afford to put more time into it.

> I had a hard enough time reading through the node.js twisty-turny
> evented code that I figured it would be hard for *me* to support it in
> production.  I've spent months doing evented programming with ruby's
> EventMachine, and eventually came up with a few techniques to keep
> myself sane.  And there are the minor deployment annoyances of adding
> node.js to every server and making sure that yet another daemon is
> running at all times.  None of these are individually deal breakers.
> But all of them together made me want to see if I could write
> something myself that I could support in production, using your
> architecture as inspiration.

> At any rate, I need an incremental iterative map reduce.  And although
> we may use Cloudant at some point in the future, locking ourselves to
> them isn't an option for us right now.  So I will continue to poke and
> prod at couch-incarnate this week; either as a reference while I build
> a library inspired by it, or as a foundation while I start using it.
Even if just as inspiration, I'm glad you find couch-incarnate useful.


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