←back to thread

Poor Man's Back End-as-a-Service (BaaS), Similar to Firebase/Supabase/Pocketbase

(github.com)
200 points dcu | 5 comments | 03 Jul 25 15:35 UTC | HN request time: 0.691s | source
Show context
CharlesW ◴[03 Jul 25 17:03 UTC] No.44457094[source]▶
Pocketbase is already the poor man's BaaS, and is minimalist compared to the two others mentioned.

> Data stored in human-readable CSVs

The choice to not use a database when two near-perfect tiny candidates exist, and furthermore to choose the notorious CSV format for storing data, is absolutely mystifying. One can use their Wasm builds if platform-specific binaries offend.

replies(6): >>44457217 #>>44457440 #>>44457602 #>>44459642 #>>44460110 #>>44460962 #
1. SOLAR_FIELDS ◴[03 Jul 25 22:23 UTC] No.44459642[source]▶
I just deployed a wasm built SQLite with FTS5 enabled and it’s insane what it is capable of. It’s basically elasticsearch entirely on the client. It’s not entirely as robust as ES but it’s like 80% of the way there, and I repeat, it runs on the client side on your phone or any other SQLite supported device
replies(2): >>44461242 #>>44462252 #
2. tommica ◴[04 Jul 25 04:58 UTC] No.44461242[source]▶
How large of a bundle is it? And are we talking about wikipedia stuffed into sqlite, or only a few hundred pages of internal docs?
replies(1): >>44466110 #
3. bsaul ◴[04 Jul 25 07:59 UTC] No.44462252[source]▶
how large is the wasm package for an empty sqlite, together with the client library to access it ?
replies(1): >>44466115 #
4. SOLAR_FIELDS ◴[04 Jul 25 16:58 UTC] No.44466110[source]▶
I'm using wa-sqlite, and the standalone wasm package is 714kb. The use case is a few hundred pages of internal docs.
5. SOLAR_FIELDS ◴[04 Jul 25 16:59 UTC] No.44466115[source]▶
the standalone wasm package is 714kb