You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that ElasticSearch is being used for storing tweets and Twitter users I think it makes sense to move our User, Trends, Places and Settings models from Redis to ElasticSearch. JSON stores more naturally in ElasticSearch without having to manually maintain id indexes. Redis will still be useful for caching and queuing work, so I think it makes sense to not remove Redis support completely.
The text was updated successfully, but these errors were encountered:
Now that ElasticSearch is being used for storing tweets and Twitter users I think it makes sense to move our User, Trends, Places and Settings models from Redis to ElasticSearch. JSON stores more naturally in ElasticSearch without having to manually maintain id indexes. Redis will still be useful for caching and queuing work, so I think it makes sense to not remove Redis support completely.
The text was updated successfully, but these errors were encountered: