Hacker News Reader

Comment by keybits | Hacker News Reader

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

View on HN

Was interested and considering switching until I saw this part:

>According to the benchmarks, Redka is several times slower than Redis.

Still a cool project, don't get me wrong. But this kind of doesn't give me any incentive to switch.

We (keydb users; it's much faster than redis for all our cases) use redka for our dev machines; we develop everything on sqlite so there is no install of anything and in prod, we just switch to our mysql, clickhouse, redis etc cluster and it all works while having a light experience for dev.

How are you guys using sqlite in dev instead of clickhouse? (Afaik there's a good bit of difference between the two dialects so I'm surprised it's possible without hurting dx through one compromise or another)

We have our own query language based on prolog which compiles to efficient queries depending on the underlying db. We haven't caught any cases for about half a decade where humans could do better queries. We are in a niche market so this is not a catch all solution; it is specifically for our market.

And I assume you have no intention of open-sourcing that query language and its compiler? Because it sounds pretty awesome...

The slowness would be inevitable because the architecture combines the weak point of Redis (network stack) with the weak point of sqlite (disk access).

It abandons Redis' in-memory data and sqlite's in-process speed... for what?

Holy cow this is amazing, I've been looking for something like this for years!!

Thanks for sharing.

Reply on news.ycombinator.com