romange

9 ms·

61.
by romange 4y ago
I think its ok that we have innovation at legal front as well. And innovation requires exploration, choosing road not taken...
62.
by romange 4y ago
Yes this problem is complex and i guess this is why it have not been solved before. We do provide atomicity guarantees for all operations like Redis! We use an algorithm from a 2014 paper - see our readme, we provide the link to the paper.
63.
by romange 4y ago
We may do it in the future. We will see if the community will accept Dragonfly with BSL. MariaDb were pretty famous and i do not remember any loud objections to their license.
64.
by romange 4y ago
By preventing them from using dragonfly. Many companies prohibit from dev teams(aka our users) from downloading and using agpl licensed software.
65.
by romange 4y ago
Redis has a BSD license because it was written by antirez who did not intend to make it a commercial enterprise. Today its too late to change and wont help Redis Inc to protect their ip. We looked at elastic, mongodb, cocroach labs, mariadb
66.
by romange 4y ago
Exactly. Finding the right balance is the right thing to do. I am not angry at cloud providers , but i am angry at OSI and their blind idealism that leaves us out there alone. I think that not solving the problem by them, hurt first of all
67.
by romange 4y ago
I do not have any practical, first hand experience with either license. Re -agpl, i know for a fact that it is banned in corporations. We choose BSL to avoid this. Say if a team in amazon would want to use DF internally they could. I know f
68.
by romange 4y ago
It does not. If you refer to Redis Modules we are not planning to support those - we can just implement same features within DF.
69.
by romange 4y ago
Well in that case, I hope to have an good answer for you. Right below the benchmark graph I deliberately put a table that shows 99th percentile lantencies at *peak* throughput as reported by memtier_benchmark. 99th latency percentile of Dra
70.
by romange 4y ago
Yes, I found many different bottlenecks. I was mostly running on AWS. In terms of hardware, for small-packets loadtests, most systems are constrained on throughput, i.e. number of packets per second. Some instances saturate on interrupts re
71.
by romange 4y ago
it could be done technically. not sure how widespread that usecase would be. dragonfly is a linking of a library and a main file dfly_main.cc so without this file you will have the lib. Redis is "Remote Dictionary Server". You gon
72.
by romange 4y ago
We will be able. It's just matter of time and priorities.
73.
by romange 4y ago
I do not know much about RDMA. Our goal is to provide a memory store that is fully compatible with Redis/Memcached protocols so that all the existing frameworks could work as before. I am not sure how RDMA fits this goal.
74.
by romange 4y ago
not yet. We are focused on building the community at this point.
75.
by romange 4y ago
You are welcomed to send a PR with the fix :)
76.
by romange 4y ago
Everyone has his dirty laundry :(
77.
by romange 4y ago
Thanks for providing your feedback. As Redis Manifesto states - our goal is to fight against complexity. antirez - you are our inspiration and I seriously take your manifesto close to heart. Please allow the possibility that Redis can be im
78.
by romange 4y ago
We do not choose AGPL so we would not harm our users. Lets not confuse the means and the goal here. AGPL is copyleft and restricting. Fair users refuse using it. OSI does not help technological companies to find a fair solution and force
79.
by romange 4y ago
I remember that I read about Anna. Very interesting paper. From what I remember that require that the operations will be conflict free. I think came to conclusion that it could be interesting as an independent (novel) store but not somethin
80.
by romange 4y ago
Not really but I read pelikan posts by twitter team. One thing in common - we both thought that cache-based heuristics can be largely improved compared to memcached/redis implementations. We did it differently though. I think our cache
81.
by romange 4y ago
no it's not us. we are two guys right now. bootstrapped with hopes that community will embrace the project and we will be able to grow the team.
82.
by romange 4y ago
btw, it's not just pretty - it has brains too. take it for a spin.
83.
by romange 4y ago
Guys, please open a bug in the repo and plus one it there :) We plan to implement everything but your votes can affect the priority of the tasks.
84.
by romange 4y ago
We compared DF with Redis OSS and KeyDB OSS, we have not used any of managed services for the comparison. AWS was used as a platform for using EC2 and cloud environment.
85.
by romange 4y ago
How you would suggest to demonstrate visually that there are no trade-offs? The tradeoff the way I see it - one needs to implement 200 Redis commands from scratch. Besides, I think DF has a marginally higher 50th percentile latency. Say, if
86.
by romange 4y ago
omg, can I marry you?
87.
by romange 4y ago
Sorry, missed your second question. Redis is using fork-based save for snapshotting and full replica sync. This means that memory pages are duplicated on write. That consumes more memory than DF implementation that implements algorithmic p
88.
by romange 4y ago
Ok you got us. We chose dragonglydb and not dragonflystore just because the former sounds better on tongue :) Having said that we carefully choose to write everywhere in the docs thay we are in-memory store (and not the database). Btw, I re
89.
by romange 4y ago
Thanks!
90.
by romange 4y ago
I've wrote in in the background section of Readme. Basically, I worked in a cloud company in a team that provided a managed service for Redis and Memcached. I witnessed lots of problems that our customers experienced due to scale probl

More ›