Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

RediSearch – Redis Powered Search Engine

oss.redislabs.com

Post reply on HN
Print view View original

21–30 of 95 posts

Re: RediSearch – Redis Powered Search Engine

#21

Post by hobofan »

teruakohatu wrote: post #13
filipn wrote: post #7

Earlier quoted context omitted.

You can read about their licenses here: https://redislabs.com/legal/licenses/ Redis Modules created by Redis Labs (e.g. RediSearch, RedisGraph, RedisJSON, RedisML, RedisBloom) are licensed under the Redis Source Available License (RSAL). Here is their RSAL license: https://redislabs.com/wp-content/uploads/2019/09/redis-sourc...

Basically you can't use it for a database product, caching engine, stream processing engine, search engine, indexing engine or ML/DL/AI serving engine. I feel just about any web app does at least one of these things.

I think the focus is on the "engine" part. What they are trying to prevent is someone else making money off of "hosted Redis".

Re: RediSearch – Redis Powered Search Engine

#23

Post by teruakohatu »

411111111111111 wrote: post #15
teruakohatu wrote: post #13

Earlier quoted context omitted.

Basically you can't use it for a database product, caching engine, stream processing engine, search engine, indexing engine or ML/DL/AI serving engine. I feel just about any web app does at least one of these things.

the correct way to phrase it would be: you cannot use it unless you pay for a licence. its source is only available so you can look at the implementation if you wish to explore the internals.

I was referring to the Redis Source Available License, I am sure if you pay enough you can modify the source too.

Re: RediSearch – Redis Powered Search Engine

#24

Post by murkt »

sam_lowry_ wrote: post #19
k_bx wrote: post #8

Earlier quoted context omitted.

But RediSearch is not based on Lucene (as claimed here https://redislabs.com/blog/search-benchmarking-redisearch-vs... )

Of course. What I mean is that the performance of distributed FTS is mostly related to its distributed aspect, not FTS by itself. If I were @aphyr, I would say that performance and correctness are competing, so a more performant distributed system is less correct, unless proved otherwise.

> I would say that performance and correctness are competing

What an interesting way to look at performance.

Re: RediSearch – Redis Powered Search Engine

#25

Post by chopraaa »

Roritharr wrote: post #11

I haven't followed Redis Modules so far, what's the best way to start the road towards prod usage if otherwise I rely on the AWS ElastiCache version?

https://github.com/RediSearch/RediSearch

Feel free to take it for a spin and learn about it. AWS doesn't (can't) include it in it's AWS offering so you'll have to buy Redis Enterprise.

Re: RediSearch – Redis Powered Search Engine

#26

Post by gkorland »

411111111111111 wrote: post #14
Roritharr wrote: post #11

I haven't followed Redis Modules so far, what's the best way to start the road towards prod usage if otherwise I rely on the AWS ElastiCache version?

I haven't used RediSearch myself for the simple reason that you need to pay for a Redis Enterprise Licence in order to use it. https://redislabs.com/redis-enterprise-cloud/compare-us/ https://redislabs.com/redis-enterprise-cloud/pricing/ thats not particularly expensive, but a dealbreaker for hobby project on which i would want to use it. sadly, there is no non-commercial licence either.

You don't have to pay for Redis Enterprise license, you can run it on self managed Redis too. You can view the RediSearch license https://github.com/RediSearch/RediSearch/blob/master/LICENSE

Re: RediSearch – Redis Powered Search Engine

#27

Post by teruakohatu »

hobofan wrote: post #21
teruakohatu wrote: post #13

Earlier quoted context omitted.

Basically you can't use it for a database product, caching engine, stream processing engine, search engine, indexing engine or ML/DL/AI serving engine. I feel just about any web app does at least one of these things.

I think the focus is on the "engine" part. What they are trying to prevent is someone else making money off of "hosted Redis".

There are additional clauses prohibiting hosting it as a service or using the source to provide a service with a compatible api.

Re: RediSearch – Redis Powered Search Engine

#28

Post by gkorland »

Roritharr wrote: post #16
411111111111111 wrote: post #14

Earlier quoted context omitted.

I haven't used RediSearch myself for the simple reason that you need to pay for a Redis Enterprise Licence in order to use it. https://redislabs.com/redis-enterprise-cloud/compare-us/ https://redislabs.com/redis-enterprise-cloud/pricing/ thats not particularly expensive, but a dealbreaker for hobby project on which i would want to use it. sadly, there is no non-commercial licence either.

I have no problem paying for it, but what I miss is a clear recommendation how to get started if you have the rather common case of your own AWS Account using ElastiCache. If I buy into the Redis Enterprise Cloud, what are it's preferred usage scenarios, how do I secure the connection properly, etc. etc. etc. This is just shoving a buy button in my face and I have no idea how to decide if what I'm buying is actually…

Redis Cloud Pro can run in your VPC.

Re: RediSearch – Redis Powered Search Engine

#29

Post by gkorland »

411111111111111 wrote: post #15
teruakohatu wrote: post #13

Earlier quoted context omitted.

Basically you can't use it for a database product, caching engine, stream processing engine, search engine, indexing engine or ML/DL/AI serving engine. I feel just about any web app does at least one of these things.

the correct way to phrase it would be: you cannot use it unless you pay for a licence. its source is only available so you can look at the implementation if you wish to explore the internals.

Not fully correct, you can change the code and even redistribute it as part of your application, as long as your application is not a "Database Product" as defined in the license

Re: RediSearch – Redis Powered Search Engine

#30

Post by elric »

sam_lowry_ wrote: post #19
k_bx wrote: post #8

Earlier quoted context omitted.

But RediSearch is not based on Lucene (as claimed here https://redislabs.com/blog/search-benchmarking-redisearch-vs... )

Of course. What I mean is that the performance of distributed FTS is mostly related to its distributed aspect, not FTS by itself. If I were @aphyr, I would say that performance and correctness are competing, so a more performant distributed system is less correct, unless proved otherwise.

CAP theorem is a little bit more nuanced than "more performance is less correct", but I see what you're saying.
Post reply on HN