Hacker News Reader

Comment by jhatemyjob | Hacker News Reader

This is a great idea and I am glad it is BSD licensed. Unfortunately the execution is somewhat lacking. SQLite is best suited for embedded / clientside applications with minimal dependencies. The author of this project decided to use Go and make it a service.

View on HN

> SQLite is best suited for embedded / clientside applications with minimal dependencies.

Often repeated and certainly rooted in truth but there was a healthy discussion on here the other day[0] where tptacek shared a link in a comment[1] to a related blog post about getting more scale out of using SQLite serverside.

0: https://news.ycombinator.com/item?id=39975596

1: https://kerkour.com/sqlite-for-servers

Did I?

> Both in-process (Go API) and standalone (RESP) servers.

In-process means that the database is "embedded / clientside" in your terms.

It's a server.

Do you usually embed redis?

I would like to.

You want to use an in-mem database like SQLite or DuckDB or even replicate the data structures in-code that redis uses. Redis doesn't really add a whole lot to the table over a general programming language with a good standard library other than being shared over a network.

Exactly, the standard library is what I'm after. I am currently using SQLite but I prefer the redis interface

What would you use Redis or substitutions for in embedded/ clientside applications? Seriously asking.

In practice iOS apps, in theory anything written in C

Reply on news.ycombinator.com