Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status, numbers, uses and unicorns #20

Open
opensam opened this issue May 21, 2013 · 1 comment
Open

Status, numbers, uses and unicorns #20

opensam opened this issue May 21, 2013 · 1 comment

Comments

@opensam
Copy link

opensam commented May 21, 2013

Hello,

hanoidb is cool for me : it "just works(TM)", it KISS heart, it may OTP and spawn rainbows. So first thank you contributors for this nice software.

I'd like to know more about the project status, real life use cases, QA feedback, fun and experiments.
I see the TODO file as a roadmap. But I don't understand its timescale or even if it is up-to-date.
I've heard about the existence of hanoidb riak rings but nothing more.

How "mature" is hanoidb today ? (it seems quite debug-ed)
What is its feature scope about data scale ? for example can a 4-cores node handle 2Terabytes of data ? under which latency, which concurrency, which R/W pattern ? max number of keys, max length of value, max whatelse ?
Are those hanoidb backed riak rings handling dozen of Terabytes ? How is the integration with riak working ? (failure handling, read repair, 2i, MP, etc)

Are there some success stories to be shared ? Which use cases, which numbers ?
I can't be the sole fan of this pure Erlang jewel ;-)

Side questions :
what are happy users of transactions saying ?
what are happy users of expiry saying ?
And where the project is heading ? (in case it has not yet reached perfection)

Thanks again

@opensam
Copy link
Author

opensam commented Mar 10, 2014

Bump. Anyone here for some feedback ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant