RediSearch – Redis Powered Search Engine • Hacker News Board

Re: RediSearch – Redis Powered Search Engine

#91

Post by softwaredoug » Thu, Jul 09, 2020, 9:58 PM UTC

dvirsky wrote: post #89

softwaredoug wrote: post #88

I’m trying to imagine why I would not use existing, mature search tech (Solr/Elastic) with existing mindshare I can hire. Why would I pay to be off on an island very locked into a proprietary search tech? Even if it is a little faster with the redis brand attached to it? It doesn’t seem quite turnkey as Algolia or as deeply featured like Lucidworks Fusion... Maybe I just don’t get the pitch yet...

You don't have to pay for it. The original license was completely Free As In Speech and even today it costs only for the distributed version. There is even a fork of it preserving the original license. It attaches to existing redis hash keys and allows you to add an index to your already existing data for example. Disclaimer - I'm the original author of RediSearch (started in 2016), before the switch to a non FOSS li…

Awesome, this is really helpful to understand what the value prop is!

The non FOSS licensing mixed with comments about needing an "Enterprise" account confused me TBH...

Re: RediSearch – Redis Powered Search Engine

#92

Post by dvirsky » Thu, Jul 09, 2020, 10:16 PM UTC

softwaredoug wrote: post #91

dvirsky wrote: post #89

Earlier quoted context omitted.

You don't have to pay for it. The original license was completely Free As In Speech and even today it costs only for the distributed version. There is even a fork of it preserving the original license. It attaches to existing redis hash keys and allows you to add an index to your already existing data for example. Disclaimer - I'm the original author of RediSearch (started in 2016), before the switch to a non FOSS li…

Awesome, this is really helpful to understand what the value prop is! The non FOSS licensing mixed with comments about needing an "Enterprise" account confused me TBH...

What I was aiming for originally beyond speed, was a simple API and an intuitive query language (https://oss.redislabs.com/redisearch/Query_Syntax/) that scales from simple textual queries to structured queries, and a big emphasis on real time incremental indexing as the core features. There is no batch vs. incremental indexing - you feed it a document and it's searchable immediately, which I thought was very important for an in memory database (it comes at the cost of avoiding some nifty index compression techniques, the compression is pretty straightforward).

But TBH it started as a demo dogfooding project for the redis module system - something to demonstrate how powerful the API is, and at the same time test it, find bugs and design problems with it, and gather real developer asks. It became the reference project for the modules API and a lot of the module system's features were designed to accommodate it (most notably async execution of slow commands).

But then a few people started using it (which all of the sudden gave redsiearch itself user asks and testing and all that), requesting features and being happy with it when these features got implemented, and it slowly started to be a thing, with people even contributing code. Then we wrote the distributed version requested by enterprise users, and it became a product, which is now developed by a team. I left it a bit over two years ago.

Re: RediSearch – Redis Powered Search Engine

#93

Post by dvirsky » Fri, Jul 10, 2020, 3:06 AM UTC

faizshah wrote: post #65

Are we pronouncing this Ready-Search, Redis-Search, or Redis-urch? Personally I vote Ready Search but I’m also in the Postgres-Sequel camp :)

Ready-Search. Source: I named it.

Re: RediSearch – Redis Powered Search Engine

#94

Post by Kerollmops » Fri, Jul 10, 2020, 8:44 AM UTC

Nice work, it’s pretty awesome to be able to plug a search engine as easily as adding a plugin. I just have one question about the recently published benchmarks, are the latency based on the two-word search "hello world"?

Re: RediSearch – Redis Powered Search Engine

#95

Post by rawoke083600 » Sat, Jul 11, 2020, 11:08 AM UTC

gkorland wrote: post #81

rawoke083600 wrote: post #59

I think it's not terrible - redis itself is just brilant ! But wow a search-redis ? I think they have a lotttt of ground to make up to compete in the search space. The amount of options/analysis/tokenization/other-search features you get out the box from anything Lucene based (solr,elastic) is just staggering.

Did you check the redisearch docs? it covers all the features you mentioned see: https://oss.redislabs.com/redisearch/#primary_features

Damn my bad ! I should have checked first ! Wow I didn't realise they that feature-complete !