-2

I have a usage case where I have to store a list of strings (max size 2520 bytes response) and finally, multiple remote clients will query multiple times (meaning a high burst of requests) to see if a domain is present in the store or not query type is going to be simple (i.e. simple one on one match and no regex is required). I am not going to use a distributed architecture (i.e. single high-performance node).

For database choice I have two options first is Elasticsearch and second is Redis. From what I have read Redis is usually faster than Elasticsearch in searching applications. If anyone knows otherwise please mention the reason.

After the choice of database, the next issue is what can be the most optimum way to store the names of domains so that their query can be faster. If anyone can guide which data structure should I use or what is the optimum way to improve the latency of queries in such a case?

1
  • You need to do your own homework and set up test environment and run benchmarks over different combinations. There are too many variables in the system that affect the choice. 2 hours ago

0

You must log in to answer this question.

Browse other questions tagged .