Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of manobi.oliveira@gmail.com
 designates 209.85.216.180 as permitted sender)
Received-SPF: pass (google.com: domain of manobi.oliveira@gmail.com designates
 10.224.185.16 as permitted sender) client-ip=10.224.185.16;
MIME-Version: 1.0
In-Reply-To: 
 <CAGnHtbJgCBkoWCNHgyk4JiorJ_o66M7RSx+ND9ZAyHqmoP3j4A@mail.gmail.com>
References: 
 <CAGnHtbJgCBkoWCNHgyk4JiorJ_o66M7RSx+ND9ZAyHqmoP3j4A@mail.gmail.com>
Date: Mon, 5 Mar 2012 13:42:08 -0300
Message-ID: 
 <CAHsaCLfsoDkRnsdkiQnt5sZjsw+QThX9bwQ1WbwOQzXe9eC3DA@mail.gmail.com>
Subject: Re: Strategy for reliable _changes feed workers
From: Gabriel de Oliveira Barbosa <manobi.oliveira@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=20cf302ef84a716cef04ba819b8c

--20cf302ef84a716cef04ba819b8c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I made a related question in
quora<http://www.quora.com/CouchDB/What-are-the-best-way-to-cache-last-seq-=
of-_changes>,
but there's no replies.

Em 5 de mar=E7o de 2012 13:23, Zachary Zolton <zachary.zolton@gmail.com>esc=
reveu:

> Hi,
>
> I've enjoyed using _changes for non-critical functionality such as keepin=
g
> a user interface up-to-date, but it also seems like a nice paradigm for
> background processing as well.
>
> For reliable background processing, my mind is inevitably drawn towards t=
he
> following questions:
>
>  * What is the last sequence number processed?
>  * Have we already attempted to process this update?
>  * How many times have we failed this update failed?
>
> Unfortunately, this all sounds like global state, which makes me feel
> un-relaxed.
>
> Now, you could help alleviate this by adding a work queue to your stack,
> but it feels like CouchDB could handle this style of processing without i=
t.
> Also, someone program would have to then sit between the _changes feed an=
d
> my background processors, which seems like a bottleneck.
>
> How are you using the _changes feed for reliable background processing?
>
>
> Cheers,
>
> Zach
>

--20cf302ef84a716cef04ba819b8c--