4 ms·
Yeah, sorry for missing Redisgraph. The entire graph is stored in memory and only spans one server. I personally am not sure what happens when that server goes
by mrjn 7y ago
Yeah, sorry for missing Redisgraph.
The entire graph is stored in memory and only spans one server. I personally am not sure what happens when that server goes down. How many minutes worth of data is lost? What's the replication strategy for another server to take over the traffic? And what about transactions and correctness?
Those things matter a lot to Dgraph users who are storing and serving their source of truths. Horizontal scalability, persistence, correctness and avoiding downtime with consistent replication have been cornerstones for the design of Dgraph.
- jacquesm 7y agoIt's a bit disappointing that you would talk down a competitor without knowing much about them, and then, to add insult to injury speculate about all kinds of things without having facts to diss them some more.
- mrjn 7y agoYou're misinterpreting me. I haven't talked down about them. And definitely don't think of them as a competitor. My point was that those questions I mentioned above are important to Dgraph users and I don't think Redis even projects itself as a persistence-first DB. I might be wrong. Either ways, our audience is quite different when it comes to enterprises at least. I know the founders of Redis Labs, met them as well and they're awesome people.
- futureastronaut 7y agoI'm more disappointed that a founder answering questions has somebody jumping down their throat for a perceived slight in a tiny portion of their reply. But that's HN.