couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zachary Zolton <zachary.zol...@gmail.com>
Subject Re: Strategy for reliable _changes feed workers
Date Mon, 05 Mar 2012 22:23:18 GMT
>
> Clearly, in BigCouch, you could not depend on the changes feed to
> ensure you process an item exactly once, so I suggest its a bad
> practice to assume the same of CouchDB. Instead, I would create a view
> that includes unprocessed items. Once processed (whatever that
> entails), update the document to indicate it has been processed. This
> will work everywhere.
>

So the view of items to be processed becomes the "global state". That make
sense!

I suppose once the view of to-be-processed items becomes empty the workers
could wait for _changes.

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