Hacker News Reader

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"?

View on HN

> 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.

The clients are the SDKs. Our docs are getting an update now to better explain how to configure clusters.

The SDKs are in separate repos currently (this is due to how university made us structure the project).

Currently we follow the memcached model so there is no replication however, remember this is straight out of university were we had to limit scope considerably and were on a tight time constraint but we aim to add data replication, consensus etc.

Reply on news.ycombinator.com