Gundb vs dgraph

Misc
1

… and I guess what I am really asking about is more like-- RAFT in dgraph vs ??? in gundb.

Gundb stores its graph across a swarm.

For the implementation I’m pursuing, this is ideal, because it’s a pretty large graph and a pretty large swarm. I think RAFT might get slow and whiny at >1k nodes.

is there a way to not replicate the entire database on every server? I’m guessing not, but figured it was worth asking.

The application will look familiar to everyone because it’s not so far off from what I’d originally set out to do with dgraph:

Ingest blockchain data and use the linjkages etween nodes to learn about the data, for:

  • bitcoin
  • ethereum
  • ethereum classic
  • dcrd
  • sia

And then of course it would be just insane if one did not attempt some useful correlations after doing the parsing. And the more real-time-ish, the likely better. I’ll post some more detail an info as this concept percolates.

and PS: If this is something that has been added to the docs, then great! I’m thumbing through now.

Lastly-- what’s the maximum sized cluster these days?

2

Dgraph splits entire cluster across thousands of Raft groups, not just one. Each group would be of size=3 or size=5. Raft works best for such group sizes.

We shard our data. We don’t replicate the entire database on every server, that wouldn’t be scalable.

There’s no maximum size for the cluster that we know of. Dgraph is meant to scale.