infinit/memo

The memo elastic and resilient key-value store.

memo's Issues

No streaming API

I would have expected a streaming API to save objects bigger than the (usable) RAM of the client.
Is this desired? Even the Value-Store API doesn't provide anything similar to this.

Are there plans to add such a API? And perhaps hand-made client libraries (go/c++ etc...)?

Status

Is this project active?

Fix: README, Invalid link to key-value vs value store document

The XXX: When shoould I use the value store against the key-value store. link in the README leads nowhere.

The key-value store uses the value store to provide a higher-level interface like common key-value stores (etcd, ZooKeeper, etc.), where arbitrary data can be stored under an arbitrary name.

The value store is the lowest brick of the architecture, providing the fundamental object named blocks, declined in a few flavors. Those blocks are cryptographically protected, their addresses are chosen randomly to guarantee a homogeneous distribution and prevent XXX(squating) and all operations are atomic, but the caller is responsible for keeping addresses.

For more details you can consult XXX: When shoould I use the value store against the key-value store.