I 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.
lol
Pocketbase – open-source realtime back end in 1 file
141–150 of 211 posts
Re: Pocketbase – open-source realtime back end in 1 file
#142The source code is structured pretty well. I really like the file abstraction that allows for both local and S3 via the interfaces.
Re: Pocketbase – open-source realtime back end in 1 file
#143Earlier quoted context omitted.
Django has great GIS integration. How does Pocketbase compare here ? Also, can Pocketbase work with PostgreSQL or is it SQLite only ?
SQLite only. I haven't come across any GIS integration. I think you should choose Pocketbase when it "not having features" and being lightweight is the feature you need.
Like Postgres has PostGIS, SQLite has Spatialite. https://www.gaia-gis.it/fossil/libspatialite/index
Unsure about integrating it with Pocketbase but I imagine it is reasonable to do.
Re: Pocketbase – open-source realtime back end in 1 file
#144Sandstorm (open source PaaS + app ecosystem) didn't make it but was encouraging to me at the time -- a standardized PaaS would seem to drastically reduce the lift to build and to host self-host things.
(No shade on compose / helm but have never had a 3rd party compose / helm thing that didn't poop the bed in some way after 6 months)
Is that happening here? Is there an ecosystem of other OSS self-host things built on pocketbase?
Re: Pocketbase – open-source realtime back end in 1 file
#145Earlier quoted context omitted.
I am so confused about this message Sounds like an sqllite performance tuning issue than anything else.
check the benchmarks here https://trailbase.io/reference/benchmarks/ its clear thats a lot of overhead on top of sqlite
https://github.com/pocketbase/pocketbase/blob/master/tools/s...
I wouldn't be surprised if that's the performance issue. It seems to be used as in memory cache for all (?) collections and uses a mutex to access them, even on reads. Most (properly set up) databases are pretty good keeping things cached and with a local socket the latency is low. With this setup I'd be very careful to do my own general purpose caching. The solution here is likely very sub optimal.
Re: Pocketbase – open-source realtime back end in 1 file
#146Trailbase is the same concept, but written in Rust instead of Go.
I started with Pocketbase but the limitation around not supporting NULLABLE columns despite being based on SQLITE was starting to become a bit of a liability, so I switched to Trailbase a little while ago.
Re: Pocketbase – open-source realtime back end in 1 file
#147The "SQLite doesn't scale" argument is usually just premature optimization masquerading as architectural wisdom.
Unless you are actively hitting WAL contention limits (which is surprisingly hard to do on modern NVMe), the operational simplicity of a single binary beats the "scalability" of a distributed mess any day.
We’ve normalized a complexity tax where every side project "needs" a dedicated DB cluster and a Redis cache. Pocketbase proves that for 99% of CRUD apps, the bottleneck isn't the database—it's the network latency and the developer's time spent managing k8s manifests.
Re: Pocketbase – open-source realtime back end in 1 file
#148Pocketbase is pretty cool, i discovered it few years ago by looking at the projects using goja at the time. since i moved to lua to avoid goja paradox.
Re: Pocketbase – open-source realtime back end in 1 file
#149Earlier quoted context omitted.
check the benchmarks here https://trailbase.io/reference/benchmarks/ its clear thats a lot of overhead on top of sqlite
https://github.com/pocketbase/pocketbase/blob/master/tools/s... I wouldn't be surprised if that's the performance issue. It seems to be used as in memory cache for all (?) collections and uses a mutex to access them, even on reads. Most (properly set up) databases are pretty good keeping things cached and with a local socket the latency is low. With this setup I'd be very careful to do my own general purpose caching.…
Thanks this is very helpful, can you please look at the code more, specially around inserts and reads why its so slow?
I am a lowly frontend developer who got into the SQLite hype due to twitter and DHH from Rails, didn't know how bad SQLite was.
Re: Pocketbase – open-source realtime back end in 1 file
#150Opened the link, went to the live app, read the first page of documentation and still doesn't know what this is.
Calls itself an "open source backend". A backend for what? Where does it fits in my application architecture? If it's a backend, can I write business rules in it? Is it a framework?