embedded key-value store, native or binding for an existing one

[paulocoghi]

Sometimes we would prefer not to use SQLite but just a simple key-value store embedded in our Crystal program

[watzon]

Just in memory? If so why not just use a hash? What specific features are you looking for?

[paulocoghi]

Thanks for the suggestion. I apologize because I forgot to mention about persistence, not just in-memory, as SQLite also provides.

When I mention embedded I mean not relying on an external software, but as a library that works internally in our same Crystal program.

[paulocoghi]

A good example in Go is BadgerDB, at https://github.com/dgraph-io/badger

It is an embeddable and persistent key-value (KV) database, but written in Go, allowing Go programs to have a persistent key-value store when not needing SQL queries.

[HCLarsen]

Sounds like it would just be a hash that's saved to a YAML file. Like secrets, but without the encryption.