redka

Redka can be used embed, in Go: https://github.com/nalgeon/redka

In similar vein, I’d always thought Redka (https://github.com/nalgeon/redka) was a neat idea since it gives you access to a subset of the Redis API backed by either SQLite or Postgres

Redka may be interesting to you: https://github.com/nalgeon/redka

Yeah, it'd be much nicer if libraries were designed to be driver agnostic, like redka which supports 4 different SQLite drivers: https://github.com/nalgeon/redka/tree/main/example

There's Redka: https://github.com/nalgeon/redka/

People reading this might be interested in Redka - Redis re-implemented with SQLite in Go: https://github.com/nalgeon/redka

Yeah, it's explained in the code[1] SQLite only allows one writer at a time, so concurrent writes will fail with a "database is locked" (SQLITE_BUSY) error. There are two ways to enforce the single writer rule: 1. Use a mutex for write operations. 2. Set the maximum number of DB connections to 1. Intuitively, the mutex approach seems better, because it does not limit the number of concurrent read operations. The benchmarks show the following results: - GET: 2% better rps and 25% better p50 response time with mutex - SET: 2% better rps and 60% worse p50 response time with mutex Due to the significant p50 response time mutex penalty for SET, I've decided to use the max connections approach for now. [1]: https://github.com/nalgeon/redka/blob/main/internal/sqlx/db....