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

Re:Poor Man's Back End-as-a-Service (BaaS), Similar to Fireb... by SOLAR_FIELDS on Thursday July 03, 2025 @06:23PM (#44459642)

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

[ Parent | on HN ]

Re:Poor Man's Back End-as-a-Service (BaaS), Similar to Fireb... by tommica on Friday July 04, 2025 @12:58AM (#44461242)

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?

[ Parent | on HN ]

Re:Poor Man's Back End-as-a-Service (BaaS), Similar to Fireb... by SOLAR_FIELDS on Friday July 04, 2025 @12:58PM (#44466110)

I'm using wa-sqlite, and the standalone wasm package is 714kb. The use case is a few hundred pages of internal docs.

[ Parent | on HN ]

Re:Poor Man's Back End-as-a-Service (BaaS), Similar to Fireb... by bsaul on Friday July 04, 2025 @03:59AM (#44462252)

how large is the wasm package for an empty sqlite, together with the client library to access it ?

[ Parent | on HN ]

Re:Poor Man's Back End-as-a-Service (BaaS), Similar to Fireb... by SOLAR_FIELDS on Friday July 04, 2025 @12:59PM (#44466115)

the standalone wasm package is 714kb

[ Parent | on HN ]