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

Should persistent in the README be reviewed? #479

Open
jeis2497052 opened this issue Jan 2, 2018 · 0 comments
Open

Should persistent in the README be reviewed? #479

jeis2497052 opened this issue Jan 2, 2018 · 0 comments

Comments

@jeis2497052
Copy link

Hi All,
diff --git a/README.md b/README.md
index 3ae3042..4bad747 100644
--- a/README.md
+++ b/README.md
@@ -493,7 +493,7 @@ Please read CONTRIBUTING if you wish to add software.

Key-Value.

    • Couchbase - In-memory, replicated, peristent key/value datastore.
    • Couchbase - In-memory, replicated, persistent key/value datastore.
    • LevelDB - Google's high performance key/value database.
    • Redis - Networked, in-memory, key-value data store with optional durability.
    • Riak - Another fault-tolerant key-value NoSQL database.

does this help?

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