81–90 of 143 posts
This seems orders of magnitude slower than Nubmq which was posted yesterday: https://news.ycombinator.com/item?id=43371097
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
Earlier quoted context omitted.
One example is when you want to display live data on a website. Could be a dashboard, a chat, or really the whole site. Polling is both slower and more resource hungry. If it is built into your language/framework, you can completely ignore the problem of updating the client, as it happens automatically. Hope that makes sense.
Interesting -- is that normally done with database updates + polling vs. something purpose-built?
You may want to search for realtime databases.
Is this suffering from the same problems like Redis when trying to horizontally scale?
Reactive looks promising, doesn't look much useful in realworld for a cache. For example, a client subscribes for something and the machines goes down, what happens to reactivity?
Earlier quoted context omitted.
I've seen this more and more with software landing pages, they are somehow so deep into developing/marketing that they totally forget to say what the thing actually is or does, that's why you show it to family and friends first to get some fresh eyes before publishing the site.
In a similar vein, lots of software is Mac-only, but omits to say this anywehere. You just get to the downloads page and see that there are only mac packages. As if nobody ever uses anything else.
Is there a single sentence anywhere that describes what it actually is?
Looks like a Redis clone. The benchmarks compare it to Redis. Description from GitHub: > DiceDB is an open-source, fast, reactive, in-memory database optimized for modern hardware. Commonly used as a cache, it offers a familiar interface while enabling real-time data updates through query subscriptions. It delivers higher throughput and lower median latencies, making it ideal for modern workloads.
Earlier quoted context omitted.
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.
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.
Anyway to persist data in case of reboots?
That's the only thing missing here.
Is Go the only SDK ?
Earlier quoted context omitted.
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