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

KeyDB CEO Interview: Getting into YC with a Fork of Redis

console.dev

Post reply on HN
Print view View original

51–60 of 77 posts

Re: KeyDB CEO Interview: Getting into YC with a Fork of Redis

#51

Post by [deleted] »

jdsully wrote: post #25
troquerre wrote: post #23

Are you concerned about AWS starting a competitor to keydb cloud/have you considered modifying your license to prevent that from happening? I'd imagine that'd be important in ensuring the long term sustainability of keydb development

They have Elasticache which is always a concern. In terms of open source projects my read is they really don’t want to run their own and are much more comfortable operating open source as a service. They “forked” Elastic Search 2 years ago and basically did nothing with it until it was re-licensed a few months ago. Now that they are investing more into it I’m interested to see how they handle it long term.

[deleted]

Re: KeyDB CEO Interview: Getting into YC with a Fork of Redis

#52

Post by sdesol »

jdsully wrote: post #25
troquerre wrote: post #23

Are you concerned about AWS starting a competitor to keydb cloud/have you considered modifying your license to prevent that from happening? I'd imagine that'd be important in ensuring the long term sustainability of keydb development

They have Elasticache which is always a concern. In terms of open source projects my read is they really don’t want to run their own and are much more comfortable operating open source as a service. They “forked” Elastic Search 2 years ago and basically did nothing with it until it was re-licensed a few months ago. Now that they are investing more into it I’m interested to see how they handle it long term.

> Now that they are investing more into it I’m interested to see how they handle it long term.

Here is an analysis of the last 30 days of activity in OpenSearch

https://public-001.gitsense.com/insights/github/repos?r=gith...

If you switch to the impact view, you can see it's pretty much one guy doing all the work right now. The impact view also shows 1 frequent, 1 occasional and 13 seldom contributors, so I'm guessing the number of people working on OpenSearch is quite small.

Note, it is also quite possible that a lot of the work is being done behind the scene, so looking at the OpenSearch repo may not tell you the whole story. And if you search for OpenSearch in amazon's job board, you find they are hiring so I guess we'll have to wait.

Note: Do not install GitSense as the docker image has an out of date license that I'll need to update when I get the time.

Re: KeyDB CEO Interview: Getting into YC with a Fork of Redis

#53

Post by gtrubetskoy »

I forked Redis to create Thredis almost 9 years ago. Some notes on how it was implemented:

https://github.com/grisha/thredis/blob/master/README-THREDIS

Then I added SQLite to it, more details here:

http://thredis.org

This was all done mostly for fun, though I did use it in a an actual project for a while.

Re: KeyDB CEO Interview: Getting into YC with a Fork of Redis

#54

Post by jdsully »

Weryj wrote: post #49

Would this mean that in a single core or low end environment, it would be better to use Redis. I'm assume cutting out multi-core complexities would be beneficial.

KeyDB is a few % slower single threaded right now, but we have some cool announcements coming in that regard.

Some people use us for Active Rep or some of our other custom commands rather than just the Multithreading.

Re: KeyDB CEO Interview: Getting into YC with a Fork of Redis

#55

Post by hardwaresofton »

Does anyone have any experience with these other Redis clones? I need to write a benchmark on these someday (the outline for the blog post is already written), but have restricted my yak shaving recently:

- https://github.com/Tencent/Tendis

- https://github.com/Netflix/dynomite

On a separate note, was FLASH (as in "flash memory") supposed to be an acronym? I've never seen people treat it as an acronym before.

Re: KeyDB CEO Interview: Getting into YC with a Fork of Redis

#56

Post by injinj »

anitil wrote: post #50
injinj wrote: post #45

Earlier quoted context omitted.

I've done a C clean room version and I will say that the networking part is as important as the multi-threading the data structures: https://github.com/raitechnology/raids/ . If you go to the landing page of the above, scroll down to the bottom, there is a TCP bypass solution graphed, using Solarflare Open Onload and it is capable of running several times as fast as the Linux Kernel TCP. I didn't test Redis with Open…

Does clean room in this case mean you didn't look at the Redis source? Is there some licensing condition where this is required?

No, I don't believe that's what it means in this case. I took the usage to mean that since Rust has memory model which is different enough from C to require a redesign.

I looked at many implementations of Redis and read many KV papers. My redesign reason was similar to a "clean room Rust" reason, I desired a memory model that used shared memory that was independent of the protocol (Redis RESP in this case), allowing multiple processes with different types of protocol services to attach to it.

Re: KeyDB CEO Interview: Getting into YC with a Fork of Redis

#57

Post by solosoyokaze »

hitekker wrote: post #48
solosoyokaze wrote: post #47

Earlier quoted context omitted.

I'm simply offering the advice that the tone seems unfriendly and is likely to be taken as such by Redis users (aka potential customers). > a person can disagree and go their own way instead of being hounded by zealots demanding compliance in the guise of friendliness This is exactly the kind of aggressive and nebulously political tone that would not help a project gain adoption. Why be hostile?

I was going to ask about where you see hostility. But judging by your comment history, it looks like you're just trolling and starting flame wars :\

Apparently you think being downvoted for believing the victim of sexual harassment (for real, check my comments) is "trolling". This community has a lot of problems.

I left my feedback for the KeyDB CEO. He can choose to take it, or not.

Post reply on HN