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

31–40 of 95 posts

Re: RediSearch – Redis Powered Search Engine

#31

Post by shawabawa3 »

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.

That's not true

> Licensor hereby grants to You a non-exclusive, royalty-free, worldwide, non-transferable license during the term of this Agreement to: ... (b) use the Software, or your Modifications, only as part of Your Application, but not in connection with any Database Product that is distributed or otherwise made available by any third party.

The license is basically to stop AWS using it as part of elasticache (or any other cloud providers)

Re: RediSearch – Redis Powered Search Engine

#32

Post by gkorland »

teruakohatu wrote: post #23
411111111111111 wrote: post #15

Earlier quoted context omitted.

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.

you can modify even if you don't pay as long as you application is not a "Database Product"

Re: RediSearch – Redis Powered Search Engine

#33

Post by [deleted] »

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.

[deleted]

Re: RediSearch – Redis Powered Search Engine

#34

Post by gkorland »

tarjei wrote: post #12
artembugara wrote: post #2

Any advantages over Elasticsearch? EDIT: I did read the article, though I overlooked the link to comparison with Elasticsearch.

One of the things I find so confusing with Elasticsearch is querying. Constructing a complex JSON document for a simple query just doesn't fit my brain. I have tried to put this down to bad/confusing documentation, but I'm not sure anymore. It seems Redis is moving a bit in the same direction - although not as complex as ES has done it. Being able to run this inside a Redis instance is a big win, although I suspect f…

RediSearch is available on all the big clouds as a managed solution

Re: RediSearch – Redis Powered Search Engine

#35

Post by sam_lowry_ »

murkt wrote: post #24
sam_lowry_ wrote: post #19

Earlier quoted context omitted.

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.

@murkt That's how I look at the performance benchmarks of distributed systems.

Re: RediSearch – Redis Powered Search Engine

#36

Post by TheRealShade »

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.

Disclaimer: I work for Redis Labs.

You can use RedisSearch on Redis Cloud Essentials with our free plan. We currently support AWS/Mumbai (ap-south-1) and we plan to gradually make it available in other regions as well.

Re: RediSearch – Redis Powered Search Engine

#37

Post by sam_lowry_ »

gkorland wrote: post #32
teruakohatu wrote: post #23

Earlier quoted context omitted.

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

you can modify even if you don't pay as long as you application is not a "Database Product"

What application is not a "Database Product", one way or another?

Re: RediSearch – Redis Powered Search Engine

#38

Post by Roritharr »

gkorland wrote: post #28
Roritharr wrote: post #16

Earlier quoted context omitted.

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.

Great. How? Is that recommended? What kind of user rights I need to give redis to manage that instance in my vpc? How to lock that down to the minimum without breaking it? In that configuration, what risks do I have to control for otherwise? ...

Re: RediSearch – Redis Powered Search Engine

#39

Post by karterk »

> Cluster Support and Commercial Version: RediSearch has a distributed cluster version that can scale to billions of documents and hundreds of servers. However, it is only available as part of Redis Labs Enterprise.

This is a bummer because high availability is really important for many search uses cases. For e.g. think about e-commerce where search literally prints money.

EDIT: it seems like the open source version supports a read-only replica for failover but my overall thoughts about not crippling/compromising the clustering story in open source version still stands.

While I understand the rationale for this move, unfortunately not having HA in a non-starter.

I had a similar temptation when open-sourcing Typesense (https://github.com/typesense/typesense) and thought long and hard about keeping clustering as part of a closed source commercial edition but eventually decided against it. I understand that commercialising certain features is a necessarily evil and trade-offs must be made. However, I think there are still many avenues to do that without keeping clustering closed source.

Apart from that, I am happy to see the search space heating up with a lot more interesting options.

Disclosure: I have stakes in the open source search eco-system (https://github.com/typesense/typesense) but a genuine Redis fan.

Post reply on HN