Apparently 1 file just means a static go binary with a bunch of separate assets compiled in. I guess for some reason I was hoping for source code that was only one file.
[deleted]
Pocketbase – open-source realtime back end in 1 file
21–30 of 211 posts
Re: Pocketbase – open-source realtime back end in 1 file
#22Is this really realtime? From looking at the description it sounds more like subscriptions to events of data changes that are dispatched close to the data operation How would realtime even work for a networked system going over tcp? https://en.wikipedia.org/wiki/Real-time_computing
Realtime in tech is considered in timespans with short delays allowed, last time i have read about it it was like 100ms.
Re: Pocketbase – open-source realtime back end in 1 file
#23Trailbase is the same concept, but written in Rust instead of Go.
TrailBase has a comparison page https://trailbase.io/comparison/pocketbase/
What a respectfully and humbly written comparison page. Ditto for their Supabase comparison. I can't rate the objectivity since I know very little about TrailBase but they got my attention now. It brings me such joy to see such a writeup in a world where humility is perceived as weakness. Kudos.
Re: Pocketbase – open-source realtime back end in 1 file
#24Been following this for some time now and it's a real delight to use. SSE subscription is really nice.
Do you use it in small projects only?
Re: Pocketbase – open-source realtime back end in 1 file
#25Is this really realtime? From looking at the description it sounds more like subscriptions to events of data changes that are dispatched close to the data operation How would realtime even work for a networked system going over tcp? https://en.wikipedia.org/wiki/Real-time_computing
Realtime in tech is considered in timespans with short delays allowed, last time i have read about it it was like 100ms.
Realtime in tech has a specific definition. The Wikipedia article covers it in more detail, but think about things like airplane wing control or space rocket computers needing to do things exactly when asked, or else people die.
Re: Pocketbase – open-source realtime back end in 1 file
#26It got some good discussion back in January, 2024: https://news.ycombinator.com/item?id=38898934 There have been a ton of releases since then. It looked like a pretty interesting project at the time. It made me want to look for a project to use it for but I never got around to it. I'd be interested to hear from people who have been using it and how keeping up with the releases has been (compatibility / breaking chang…
I've been using it for a while. There was only one release that required manual migrations. I think 0.23.0 and apparently the dev is backporting security updates for those who haven't upgraded. I use Go so all I have to do is `go get -u` and `go mod tidy` and then it's upgraded. It works great.
How is it in production? Does it it live up to your requirements?
Re: Pocketbase – open-source realtime back end in 1 file
#27Is this really realtime? From looking at the description it sounds more like subscriptions to events of data changes that are dispatched close to the data operation How would realtime even work for a networked system going over tcp? https://en.wikipedia.org/wiki/Real-time_computing
There is realtime, and there is "realtime". The other one being realtime in apps doing some sort of music thing, flight controllers etc. Then there is web "realtime" that basically only means 2sec in the past-realtime.
Re: Pocketbase – open-source realtime back end in 1 file
#28Re: Pocketbase – open-source realtime back end in 1 file
#29I can vibe code this in rust in a day most
Re: Pocketbase – open-source realtime back end in 1 file
#30Congrats on the launch!