• Catalog Search
  • Autocomplete
  • Catalog Search
  • Autocomplete
  • Document Search
  • Secondary Index
High performance search scenarios such as the above require engines optimized for simultaneous indexing and querying. Traditional disk based search engines are often easily outpaced in high volume, high performance situations and cannot keep up with the user experience needs. Most traditional disk based databases, in turn, require high performance secondary indexing to keep up with user interactivity requirements.

How Redis Enterprise Makes Search Easy

Why Search is Hard With Other Databases:


Too slow:

Most other search solutions rely on slow, disk-based indexing and define “real-time” as minutes or hours from index to query availability.

Too complex:

Other search solutions require deploying additional stacks of servers, virtual machines, coordination layers and libraries.

Can’t Scale:

Other search solutions struggle as they cluster to many nodes, providing diminishing performance returns.

Why Redis Enterprise for Search

Real time:

RediSearch is true real time, 1 millisecond from indexing to query availability.

Least complex:

RediSearch is implemented as a module inside Redis Enterprise and can be utilized through standard Redis libraries, no new software to manage nor libraries to integrate.

Scales like a champ:

RediSearch is optimized for both fully connected Fan-in/Fan-out as well as tree-based fan-in/fan-out to deliver a consistent performance to scale.

Related Resources

RediSearch: A High Performance Search Engine as a Redis Module
From Reds to RediSearch: Redis search got a lot more interesting