I only learned this morning that that's a thing that Redis advertises as capable of. However, I cannot find many case studies to establish how viable/practical is using Redis for this use case.
You need very fast search on a relatively small dataset. Your search patterns are simple and well-defined. You're already using Redis as your primary database. Low latency is critical.
Choose Elasticsearch when:
You have large amounts of text data. You need advanced search features and relevance tuning. Your data is semi-structured or unstructured. You need sophisticated analytics capabilities. Scalability is a primary concern
Below 10M documents for single node. Below 100M documents for clustered setup. Total data size (including indices) that can comfortably fit in available RAM.
4 comments
[ 4.9 ms ] story [ 16.0 ms ] threadYou need very fast search on a relatively small dataset. Your search patterns are simple and well-defined. You're already using Redis as your primary database. Low latency is critical.
Choose Elasticsearch when:
You have large amounts of text data. You need advanced search features and relevance tuning. Your data is semi-structured or unstructured. You need sophisticated analytics capabilities. Scalability is a primary concern
For someone that could be 1m records for others that could be 1bn records