Comment by tiffanyh
2 years ago
So it's the "Supabase of SQLite"?
Aren't there entire classes of problems that shouldn't exist for SQLite because it's intended to be an embedded database, as opposed to a client/server architecture like Postgres/Supabase?
And as such, I'm confused why this exists.
>And as such, I'm confused why this exists.
Beyond the standalone server mode, I'm able to literally import this as a library/framework right into my Go app (https://pocketbase.io/docs/go-overview/). Having a single binary that contains my custom business logic + a very nice DB/Auth/Admin/... is a very compelling option.
PocketBase is trying to be a simple webserver, code-running backend, and database. I believe the author chose SQLite because it is simple. PocketBase isn't trying to have every feature nor be high performance.
Like Althttpd?
That’s the web server created by the SQLite team and also serves sqlite.org
https://sqlite.org/althttpd/doc/trunk/althttpd.md
Thanks for bringing it to my attention, never heard of it before. Have you used it?
It's very common to use SQLite within backends, whenever concurrency is not a big issue.