Live data from Hacker News

Show HN: PocketBase – Open Source realtime backend in one file

github.com

81–90 of 113 posts

Re: Show HN: PocketBase – Open Source realtime backend in one file

#81
post #79
post #70

Nice but my super anal quip is please don't call this thing "realtime". It doesn't make sense in this context. What is realtime about it? Are there timing guarantees or are timing constraints provided in API requests? Because that's what realtime systems are. Realtime does not mean "real fast". For example, a train track switching system might be getting run by a 1MHz CPU and still be real time. It's not about speed,…

It’s not a real-time operating system. In this case, real-time means it is built such that a client gets access to updated database values as soon as they change, as opposed to a non real-time database which doesn’t necessarily have a built-in mechanism for reliably on time updates.

You mean like eventual consistency vs immediate consistency? Because a database that reflects its changes at the end of a transaction is called an ACID database not a real-time database.

Re: Show HN: PocketBase – Open Source realtime backend in one file

#84
post #44

PocketBase is a small open source project that I've been working for the last couple of months. You could think of PocketBase as a lightweight Firebase/Supabase alternative. In short, it is an open source Go backend (framework and app) consisting of: - embedded database (SQLite) with realtime subscriptions\ - backed-in files and users management - convenient Admin dashboard UI - simple REST-ish API And all of this co…

feedback: the "in one file" marketing confused me for a bit until i realized you meant "as a single binary". i would say that instead.

I got tripped up on the same thing.

Re: Show HN: PocketBase – Open Source realtime backend in one file

#87

Potentially silly question (I'll go out on a limb anyway). I would like to create a multi-platform app for non-technical users where their data is transparently self-contained/self-hosted. So, they open a single binary and it presents them with a UI, and the data created from within the app would be stored in their local PocketBase database. However, I wouldn't want the user to have to start a server directly (they w…

Checkout wails.io and tauri.app

Re: Show HN: PocketBase – Open Source realtime backend in one file

#88

Earlier quoted context omitted.

The pex tool lets you build single file python executables which are well suited for server deployments.

oh wow thanks i didn't know about this. in that case it would be super simple for me to wrap up a FastAPI server with SQLite or even some in-memory database that runs elsewhere, deliver as a single file!

Yeah this kind of thing was common when I worked at Twitter (where AFAIK pex/pants was developed) on an infrastructure team. It's a cool tool that few outside of Twitter seem to be aware of.

Re: Show HN: PocketBase – Open Source realtime backend in one file

#89
post #78

Earlier quoted context omitted.

The pex tool lets you build single file python executables which are well suited for server deployments.

How big is a python3 runtime when pex has packaged it up? And do you happen to know what the output binary is linked to?

As I recall, pex doesn't package up the runtime. It essentially packages up your venv, code, and resources and runs them under an installed runtime. It makes use of a relatively unknown bit of python functionality, which is that CPython will try to treat a zip file as a valid python script.

Re: Show HN: PocketBase – Open Source realtime backend in one file

#90
post #85

This is fantastic work. Supabase local development has always been a pain.

Member of the Supabase team! Would love to hear your pain points with local development. Always looking for feedback so that we may improve your experience.

Well all the UI stuff. It is super easy to add a column and change something fast with the UI when doing rapid development. But that piece is missing when developing locally. I have gone on to create 2 projects (one called local and one prod) and manually applying the changes. Would be nice to apply changes from one project to another. PocketBase here for example provides the UI locally too. That is the real selling point IMO.
Post reply on HN