Different tool. I metrics I am optimizing for are different hence wrote a separate utility. May not be the most optimized one. But I am usign this to measure all things DiceDB and will be using this to optimize DiceDB further.

ref: https://github.com/DiceDB/membench

The benchmark tool is different. I mentioned the same on my benchmark page.

We had to write a small benchmark utility (membench) ourselves because the long-term metrics that we are optimizing need to be evaluated in a different way.

Also, the scripts, utilities, and infra configurations are mentioned. Feel free to run it.

Yes. I do run a sys design course on weekends.

We had a similar thought, but it is not as bad as we think.

We have the benchmarks, and we will be sharing the numbers in subsequent releases.

But, there is still a chance that I may come to bite us and limit us to a smaller scale, and we are ready for it.

Vertical scaling this language also gets into painful territory quite often, I’ve had to workaround this problem before but never with a thing that felt like this: https://github.com/tailscale/tailscale/blob/main/syncs/shard...

Why are you guys building Yet Another DB ? Not trying to dissuade you, but what are you trying to solve that the plethora of DB's currently in market in the same space have not solved ? This should be highlighted in your landing page and since your primary audience is other dev's ( tough-est crowd to sell ), be very specific on what value your product brings over the other choices.

it might help to add 99th percentile numbers to the landing page; would do a better job of showing GC impact.

Nope. We are not redis compliant.

Yes. With DiceDB clients can "WATCH" the output of the commands and upon the change in data, the resultset are streamed to the subscribers.

I prefer that over X icon.

nope. We do not support Redis protocol :)

Did you remove support? Cause Google found mentions of it on your website.

Heh. Redis protocol support is still listed on their Linkedin. https://www.google.com/search?q=%22DiceDB%22%20%22supports%2...

Nope. it started as Redis clone. We are on a different trajectory now. Chasing different goals.

> Chasing different goals.

What are those goals? I was struggling to interpret a meaningful roadmap from the issue & commit history.

Secret goals are no selling point.

Arpit here.

DiceDB is an in-memory database that is also reactive. So, instead of polling the database for changes, the database pushes the resultset if you subscribe to it.

We have a similar set of commands as Redis, but are not Redis-compliant.

Would "key-value" not have a place in the description?

This application may be very capable, but I agree with the person saying that its use-case isn't clear on the home page, you have to go deeper into the docs. "Smarter than a database" also seems kind of debatable.

This is a lot clearer than any information I found anywhere else. There wasn't any room on your website, README, or docs for this summary?

This is a common enough pattern that it should have a name, where the submitted link isn't clear, but a single comment on HN is.

The Cravens Conjecture

It is right there on the landing page. But, let me highlight it a bit.

When I ctrl+F the landing page for key and value, I find nothing. Reading it in full, I also come up empty handed. Which part of the landing page implies it's a key value store?

They did not say anything about key/value in their message.

You are absolutely right, my bad.

IMO, replace "More than a Cache. Smarter than a Database." with an actual description.

The saying is cute but does not really convey information the reader is after. And that spot is where you want people to immediately understand what it is.

I changed that :) now the value proposition is right at the top.

Still not clear to me what it is. Only the features it has, without knowing what it is.

Like, imagine a page that only said "SuperTransport -- 0 to 100 in 5 seconds", but it is not clear for the reader if it is a car or a horse or a plane or a parcel service...

... and the reader has to go and guess "hmm, guess due to the acceleration it is probably a car or a motorbike -- wonder of it is for sale or for rent?".

Just put "fast on premise key/value database" in the big font that was there -- if that is what it is. That is purely a guess from me, no idea if that is what it is.

In the list of things that DiceDB is at the top, you should add "an in-memory database". Pretty critical thing to leave out right at the top.

in-memory key-value store seems much more accurate

So like RethinkDB? https://rethinkdb.com/

Not a month goes by where I don’t remember it at least once and realize that I still miss it.

This seems more like Redis though

It kinda surprising it was never really continued, but performance was just too bad even if the interface was fantastic.

Why don't you run the open source version?

I did for about a year and the issue is that ORMs have issues and maintainers don't feel the need to make changes.

Question, how does DiceDB differ from Redis pub/sub? https://redis.io/docs/latest/develop/interact/pubsub/