Thanks for your suggestions. I’ve gone ahead and updated the README, to
reflect the same and appreciate your suggestions on that as well.
I hadn’t thought about riak_core/riak_ensemble. Will check it out. As for
CRDTs, isn’t that a little loose with it’s consistency guarantees? I was
considering those, but Redis is very strong with it’s consistency
guarantees, so I’d like to have RemixDB meet those as well.
Best,
Santosh
Appreciate your response as well. Misleading is definitely a bit of a stretch, since a whole slew of sections are TBD’ed. I’ve gone and thrown in a disclaimer now, so it should be more obvious now.
And yes, I’m in complete agreement, supervisors/other OTP constructs are definitely something that will be there when it’s usable and are a high priority. RIght now, as Sasa had picked up, it’s more of a playground than anything else. But should be usable real soon.
Best,
Santosh
According to the (admittedly 3 years old) analysis by Kyle Kingsbury (aka Aphyr), Redis offers no real guarantees. This recent article by Martin Kleppmann is also an interesting read on the topic.
My takeaway is that Redis is not consistent, so it’s only suitable for some nice-to-have caches. Disclaimer: I didn’t follow the development of Redis for past few years, so perhaps something has improved here.
@santosh79 This is a small nit-pick but it would also be a good idea to include a license in your project. Potential contributors might be discouraged from helping out if they don’t know to what degree the code belongs to the community.
+1. I always look at Scala code and just appalled by the ! all over the place. I love that you provided a list of excellent points too. I should learn how to implement a Redis protocol too. 
I applaud the effort @santosh79!
@santosh79 are you still actively working on this, or was it more of an exploratory / learning exercise?
Hi Steven,
I’ve been working on a branch and haven’t pushed up stuff yet. Will be
doing it shortly. Still under active maintenance.
Best,
Santosh