On Tue, Sep 23, 2008 at 1:07 AM, Dustin <[EMAIL PROTECTED]> wrote: > > > On Sep 22, 6:51 am, "Steve Chu" <[EMAIL PROTECTED]> wrote: > >> MemcacheQ is a damn simple queue service over memcache protocol, just >> set for append and get for consume. Any memcached clients can do queue >> operations on MemcacheQ. It is very fast, and can do tens of thousands >> append/comsume operations per second. > > Does it block? Yes, we can not say it does not block, but it runs fast:)
> > Does it ever drop queued items? No, it is persistent(we use Berkeley DB TDS in our backend). But for '-N' mode, if the server daemon crashed, it will lose the data in the write buffer(the size determined by you with '-L' option), seem we should use replication for this situation, but a bit complicated. > > Can you compare it to gearmand/beanstalkd/starling? > We need a queue component that we know all the details(I mean the code base, and when something bad happened, we can solve it easily). We do not use Perl, we do not use Ruby, so we do not use gearmand and starling. The application developers in our company are very familiar with memcached clients, so we take the memcache protocol as a consideration. -- Steve Chu http://stvchu.org
