GhostDB – A Fast Distributed Cache • Hacker News Board

GhostDB – A Fast Distributed Cache

#1

Post by GhostDBCache » Wed, Jul 08, 2020, 9:00 PM UTC

GhostDB – A Fast Distributed Cache
github.com

Re: GhostDB – A Fast Distributed Cache

#2

Post by nodesocket » Thu, Jul 09, 2020, 12:44 AM UTC

Great project. I did not see an explanation on the architecture of a cluster. Is data replicated to all nodes, or is data only stored on a single node (sharded). What happens when a node in the cluster goes down? Does there have to be a consensus (odd number of nodes) for the cluster to be "healthy"?

Re: GhostDB – A Fast Distributed Cache

#3

Post by cmckn » Thu, Jul 09, 2020, 12:50 AM UTC

nodesocket wrote: post #2

Great project. I did not see an explanation on the architecture of a cluster. Is data replicated to all nodes, or is data only stored on a single node (sharded). What happens when a node in the cluster goes down? Does there have to be a consensus (odd number of nodes) for the cluster to be "healthy"?

> GhostDB provides a very large hash table that is distributed across multiple machines.

Sounds like no replication to me, AKA the memcached model. I can't find how to actually configure a cluster (the `Cluster Configuration` section of the docs doesn't contain anything related to hosts). I also can't find anything client side that would distribute requests to a list of nodes with a consistent hash, for ex. I can't find a client at all, actually.

Still, interesting project, kind of aiming for Redis features and a memcached topology.

Re: GhostDB – A Fast Distributed Cache

#4

Post by iammru » Thu, Jul 09, 2020, 1:00 AM UTC

Doesn't Redis already address all of this?

Re: GhostDB – A Fast Distributed Cache

#5

Post by cmckn » Thu, Jul 09, 2020, 1:05 AM UTC

iammru wrote: post #4

Doesn't Redis already address all of this?

Yes, probably with superior performance. The clustering model seems to differ, but as far as I can tell, the 'distributed' part of this project isn't really implemented.

Re: GhostDB – A Fast Distributed Cache

#6

Post by AlphaSite » Thu, Jul 09, 2020, 2:17 AM UTC

Is this similar to geode/gem fire?

Re: GhostDB – A Fast Distributed Cache

#7

Post by trishume » Thu, Jul 09, 2020, 2:37 AM UTC

“microsecond performance” irks me because you can’t get latencies of a microsecond without very expensive special network cards and APIs which they don’t seem to mention and I doubt they use. So they either mean 10s to hundreds of microseconds or they’re taking the reciprocal of their throughput which would be weird and misleading.

If you’ve made a fast product that’s great! Show us with well-explained benchmarks not the term which sounds best but you can still hand wave as justified, because it’ll make people suspicious.

Re: GhostDB – A Fast Distributed Cache

#8

Post by Icyphox » Thu, Jul 09, 2020, 2:53 AM UTC

Fucking Discord for an open source project.

Re: GhostDB – A Fast Distributed Cache

#9

Post by matt_f » Thu, Jul 09, 2020, 3:03 AM UTC

Could anyone explain a use case for this? (Distributed KV store)

Genuine question, thanks

Re: GhostDB – A Fast Distributed Cache

#10

Post by dallbee » Thu, Jul 09, 2020, 3:23 AM UTC

trishume wrote: post #7

“microsecond performance” irks me because you can’t get latencies of a microsecond without very expensive special network cards and APIs which they don’t seem to mention and I doubt they use. So they either mean 10s to hundreds of microseconds or they’re taking the reciprocal of their throughput which would be weird and misleading. If you’ve made a fast product that’s great! Show us with well-explained benchmarks not…

Or, perhaps, they're taking the non-networked use case.