Using an instrument of chance to name a data store technology is pretty amusing to me.
This is essentially what all in-memory data stores have always been
Kinda refreshing to see someone own it and run with it
DiceDB
101–110 of 143 posts
Re: DiceDB
#102I like it! Anyway to persist data in case of reboots? That's the only thing missing here. Is Go the only SDK ?
Snapshot functionality is WIP, which can be utilised to persist and replay data between reboots.
For now Golang SDK is only one, more SDKs are to be added soon.
Re: DiceDB
#103There are _so many_ bugs in this code. One example among many: https://github.com/DiceDB/dice/blob/0e241a9ca253f17b4d364cdf... defines func ExpandID, which reads from cycleMap without locking the package-global mutex; and func NextID, which writes to cycleMap under a lock of the package-global mutex. So writes are synchronized, but only between each other, and not with reads, so concurrent calls to ExpandID and NextI…
Haven't looked at the code, but enforcing mutual exclusion between writers but not readers can make sense for a single-writer lock-free algorithm.
> single-writer lock-free algorithm
I understand the need for correct lock-free impls: Given OP's description, simply avoiding read mutexes can't be the way to go about it?
Re: DiceDB
#104DiceDB sounds like the name of a joke database that returns random results.
No it doesn't.
Re: DiceDB
#105I feel like this needs a ‘Why DiceDB instead of Redis or Valtio’ section prominently on the homepage.
Did you mean Valkey, or has the js community now managed to shoehorn an entire high-availability database server into a javascript object proxy?
Re: DiceDB
#106Earlier quoted context omitted.
Can't wait to feel the impact of garbage collection in my fast cache!
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.
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.
Re: DiceDB
#107Earlier quoted context omitted.
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.
Not 100% a Redis clone, but the API appears to be very similar to Redis of 10 years ago, with some additions that Redis doesn't have. See the list of commands: https://dicedb.io/get-started/installation/
"clone" was not the right term, maybe Redis-look-alike, or something along those lines, something that can be compared to Redis, at least.
Re: DiceDB
#108Re: DiceDB
#109Earlier quoted context omitted.
No it doesn't.
It was my first thought as well, before reading the landing page.
Yeah, and I'm sure someone clicked it thinking it was a DB for EA's Dice Studios.
If you expose something to enough people you'll get some unreasonable takes and interpretations of it. It's important to ignore them.