I am curious to better understand the benchmarks against simple SQLite, especially under typical load. Any level of latency will be an unnecessary overhead.
Pocketbase – open-source realtime back end in 1 file
31–40 of 211 posts
Re: Pocketbase – open-source realtime back end in 1 file
#32Earlier quoted context omitted.
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?
Yes, I use it with an RSS reader and an email app and it works great.
Re: Pocketbase – open-source realtime back end in 1 file
#33Apparently 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.
Same here. At first, I thought it was a one-file-based database, which would have been even more commendable.
Re: Pocketbase – open-source realtime back end in 1 file
#34Earlier quoted context omitted.
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.
Even that stuff has a delay.
Re: Pocketbase – open-source realtime back end in 1 file
#35Is 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
I believe there is no contradiction with the definition from the linked article?
> A system is said to be real-time if the total correctness of an operation depends not only upon its logical correctness, but also upon the time in which it is performed. Real-time systems, as well as their deadlines, are classified by the consequence of missing a deadline:
> Hard – missing a deadline is a total system failure.
> Firm – infrequent deadline misses are tolerable, but may degrade the system's quality of service. The usefulness of a result is zero after its deadline.
> Soft – the usefulness of a result degrades after its deadline, thereby degrading the system's quality of service.
From what I can tell, https://pocketbase.io/ attempts to be a soft-realtime system.
Re: Pocketbase – open-source realtime back end in 1 file
#36Database, admin, auth... is this some kind of Go's Django ?
Re: Pocketbase – open-source realtime back end in 1 file
#37I can vibe code this in rust in a day most
No, simple answer. Try it, link to the repo and I will tell you all the placed it failed. Vibe coding has its places. For something like pocketbase it most definitely is not ready yet.
Re: Pocketbase – open-source realtime back end in 1 file
#38Is 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.
Heh. I wasn't aware that there was a new definition of realtime. My 40+ year career consisted of about 20% realtime embedded firmware development. In all of my experience, 100ms is an absurdly long delay. Most RTOSs (that call themselves such) have latency measured in μs. The last serious RTOS that I wrote (MSP430, non-preemptive) had a firm requirement that any task must complete within 1ms. That one ran on a single threaded MCU clocked at 25MHz. It had a unix-like scheduler, with prioritized tasks, and I even threw in a 'top' display that showed per-task MCU usage, and load average.
Re: Pocketbase – open-source realtime back end in 1 file
#39Earlier quoted context omitted.
Realtime in tech is considered in timespans with short delays allowed, last time i have read about it it was like 100ms.
Heh. I wasn't aware that there was a new definition of realtime. My 40+ year career consisted of about 20% realtime embedded firmware development. In all of my experience, 100ms is an absurdly long delay. Most RTOSs (that call themselves such) have latency measured in μs. The last serious RTOS that I wrote (MSP430, non-preemptive) had a firm requirement that any task must complete within 1ms. That one ran on a single…
Well Pocketbase isnt embedded firmware.
Re: Pocketbase – open-source realtime back end in 1 file
#40I've been trying out Pocketbase on a side project idea. I'm super impressed!
Having worked for many years on Django projects, Pocketbase seems like a perfect fit for those small to medium sized projects for which you don't want to create and maintain a traditional backend for.
Happy to answer any questions.