Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A awesome-sysadmin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 189
    • Merge requests 189
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Francisco Augusto
  • awesome-sysadmin
  • Issues
  • #479
Closed
Open
Issue created Jan 02, 2018 by Administrator@rootContributor

Should persistent in the README be reviewed?

Created by: jeis2497052

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?

Assignee
Assign to
Time tracking