So I'm looking at the streaming api (track), and I've got thousands of
searches. ( http://tweettronics.com ) I mainly need it to deal with
terms that are very high volume, and to deal search api rate limiting.
The main difficulty I'm thinking about is the best way to de-multiplex
the stream back
So I'm looking at the streaming api (track), and I've got thousands of
searches. ( http://tweettronics.com ) I mainly need it to deal with
terms that are very high volume, and to deal search api rate limiting.
The main difficulty I'm thinking about is the best way to de-multiplex
the stream back
One idea off the top of my head: write tweets to something like Lucene, and
then rely on its more sophisticated query engine to pull tweets. You'll
sacrifice some latency here of course.
---Mark
http://twitter.com/mccv
On Fri, Apr 16, 2010 at 3:47 PM, Jeffrey Greenberg
I know it's not Web 2.0-cool, but I'm writing to SQL Server 2008
(Standard, x64) and using fulltext indexing/searching from there. On
production hardware, I hardly see any real impact as far as latency
goes, even on busy predicates. I can't imagine that the
lighter-weight/more efficient Lucene
