Indexing is pretty fast these days as you noted regarding (on the extreme end) Twitter, so I highly doubt this'd be an issue for most apps. If it is then maybe they should use Kestrel (https://github.com/robey/kestrel) from Twitter or some other similar MQ system?
On Mon, Feb 14, 2011 at 12:22 PM, Ted Dunning <tdunn...@maprtech.com> wrote: > Upon success, the composer of the message should be told as soon as possible > that their message has been committed. If it is indexed before they can > formulate a query, then all is well. There is no need to delay completion > of the update IMO. > > On Mon, Feb 14, 2011 at 12:18 PM, Jason Rutherglen < > jason.rutherg...@gmail.com> wrote: > >> > I almost always prefer write-behind indexing of some kind. >> >> I think that's the easier of the two methods and while it can be >> accomplished in this system, would require some sort of 'queue' etc. >> For things like messaging, eg, email, a database write and subsequent >> document analyze should be fast, and should upon success, be >> searchable? >> >
