pglite VS pocketbase

Solving this is high on my list with PGlite (https://github.com/electric-sql/pglite). I have a bunch of iteas/thoughts that I hope to get to at some point.

Hey HN! For a few months, I've been building pgmock at work for our E2E and unit test suite. It emulates Postgres in WebAssembly and has full feature parity with production databases.

The cool thing about it is that you don't need any external processes or proxies. If your platform can run WASM (Node.js, browser, etc.), it can probably run pgmock. Creating a new database with mock data is as simple as creating a JavaScript object.

It's a bit different from the amazing pglite [1] (which inspired me to open-source pgmock in the first place). While pgmock runs an x86 emulator, pglite compiles a Postgres fork to native WASM directly and is hence much faster and more lightweight. However, it only supports single-user mode and a select few extensions, so you can't connect to it with normal Postgres clients (which is quite crucial for E2E testing).

Theoretically, it could be modified to run any Docker image on WebAssembly platforms. Anything specific you'd like to see?

Happy hacking!

[1] https://github.com/electric-sql/pglite

I've found postgres via docker to be fine for dev and testing, but there are various epheremal postgres scripts, plus this could be promising for node stuff https://github.com/electric-sql/pglite if it works out. I'd imagine if this does work out we'll see the same kind of builds for other runtimes as well (like python)

> Use SQLite for everything, or Postgres if you outgrow it.

Or both! ElectricSQL syncs front end SQLlite back to server side postgres. And they just rebuilt postgres on pure WASM (https://github.com/electric-sql/pglite). All ties together with a CRDT.

I'm not affiliated, but just think it's just cool to imagine calls to front end sqllite as the be-all-end-all.

the logo is already taken by https://pocketbase.io

Pocketbase - Never used before but it says in their home page the following: "Open Source backend for your next SaaS and Mobile app in 1 file". Seems porwerful.

Solutions like pocketbase and coolify come close to solving these problems. However, I wouldn't choose either as I fear architecture lock-in as much as vendor lock-in. Especially in the case of pocketbase, I may be forced to rewrite my application if it were to scale overnight.

Now, I've released the Gowebly CLI v2.5.0 which includes PocketBase framework/backend support.

It's an obvious question, but have you looked into Pocketbase?

https://github.com/pocketbase/pocketbase

I'd like to plug PocketBase [0] for a similar use case.

Last week I was looking for a place to store random data with API access, and was looking at making a Google Sheets backend, but PocketBase was easy and didn't have a 60 rpm quota.

Deploying to a cheap VPS was very easy with CapRover.

[0] https://pocketbase.io/

What is Pocketbase? Pocketbase is an open-source backend solution offering a real-time database, file storage, and seamless user authentication with OAuth integration, all readily available right out of the box.

Browsing HN, GitHub and the like we get to see a huge variety of software products and code bases.

I often see products and think - if this product X, got together with Y, it would be pretty cool - kind of like if they had a kid together.

Not too literally, but more on the conceptual level - my level of programming is low.

E.g. Just some....

- pocketable.io & datasette (+with some more charting) [https://pocketbase.io, https://datasette.io]