Really a database is the way to go. Any modern database should allow
you to check if a value is in there before inserting, so the same
tweet won't go in there twice. Additionally, not every user search has
to use the up to the minute results. They can go back just a little in
time (30 seconds or
Try memcached.
- @NeluLazar
On Oct 2, 7:36 am, Bjoern bjoer...@googlemail.com wrote:
Hi,
just wondering about a best practice thing. Suppose I show results of
specific Twitter searches on a web site. How would I go about caching
the searches?
The naive approach seems to be to first
