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.
Show HN: PocketBase – Open Source realtime backend in one file
81–90 of 113 posts
Re: Show HN: PocketBase – Open Source realtime backend in one file
#82I've tried them out for some dummy projects and they seem pretty great, and they are continually iterating and pushing new features.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#83Re: Show HN: PocketBase – Open Source realtime backend in one file
#84PocketBase 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.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#85This is fantastic work. Supabase local development has always been a pain.
Would love to hear your pain points with local development. Always looking for feedback so that we may improve your experience.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#86All of this extra complexity associated with multi-tiered multi-microservice arch is not needed for many categories of apps, and especially for small teams.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#87Potentially 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…
Re: Show HN: PocketBase – Open Source realtime backend in one file
#88Earlier 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!
Re: Show HN: PocketBase – Open Source realtime backend in one file
#89Earlier 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?
Re: Show HN: PocketBase – Open Source realtime backend in one file
#90This 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.