trailbase

10 ms·

1.
by trailbase 10mo ago
Switching DBs is very invasive. Switching your application base even more so. As long as you're happy happy with PocketBase and there's nothing you're critically missing, the answer will almost certainly be: no. Is there anyt
2.
by trailbase 10mo ago
(Similar disclaimer: I'm not an expert on PocketBase implementation details) I don't think the referenced `Store` is used in the SQLite access path and PocketBase uses SQLite in WAL mode. Besides, in cases where the `Store` is use
3.
by trailbase 10mo ago
Thank you! This is great feedback. Much appreciated.
4.
by trailbase 10mo ago
I'm guess but it probably depends on who's being choked here. If it's the caller, then it may be the overhead of individual deletions for each record when using the record APIs. If other users are being choked, it may refer t
5.
by trailbase 10mo ago
Self-hosted Supabase is pretty good. I don't think anyone argues with that. It didn't used to be as smooth and it's certainly hungrier with many more moving parts. Could you elaborate a bit more on your scaling concerns? You
6.
by trailbase 10mo ago
The most well-known ones are probably: Supabase, AppWrite and PocketBase.
7.
by trailbase 10mo ago
> I guess I just have to accept that the term has lost it's meaning at this point and can be used for whatever whoever wants to use it for It's maybe more like you point out: realtime in the OS context vs realtime in an event p
8.
by trailbase 10mo ago
Can easily go either way. If you're comparing in-process SQLite to talking to SQLite over HTTP you'll probably get a small penalty for any language. When co-located on the same machine, you can probably expect something like ~5ms
9.
by trailbase 10mo ago
Love seeing the love for SQLite. Personally, I've had a great experience with litestream, which will continuously replicate any changes. Are you using https://sqlite.org/rsync.html ?
10.
by trailbase 10mo ago
Thanks! Standing on the shoulders of giants :heart:
11.
by trailbase 10mo ago
You won't get any argument here. PocketBase's is very polished and friendly. I fell back onto a popular pre-existing UI component system called shadcn (which does look a bit like bootstrap), not only because you gotta start somewh
12.
by trailbase 10mo ago
Hi! Depends on what you mean by "any JS". Many JS ecosystems depend on an environment. For example, there are browser environments where you get a common baseline with some vendor differences, there's the server where you get
13.
by trailbase 2y ago
Makes sense. If it's mostly auth you're after, there's a bunch of dedicated products: https://github.com/zitadel/zitadel , https://github.com/teamhanko/hanko , https://gith
14.
by trailbase 2y ago
Got it. Sounds like you're in the market for a SQL database. In your setup, is there anything extra you'd want? I guess I'm merely wondering what FireBase and Co could even provide to you?
15.
by trailbase 2y ago
> In WAL mode SQLite is very good at supporting parallel reads from multiple threads. It should only block for a long time when writing (since writes require an exclusive lock.) Agreed. > It sounds like your v8 worker threads are mixi
16.
by trailbase 2y ago
> My initial comment was more of a note/suggestion to simply list the used versions of the tested platforms (not just for PocketBase) because often they change over time and the shown results could be misleading if someone stumble o
17.
by trailbase 2y ago
Could you expand a bit on, how > I feel I prefer to have a locked-down database, and implement everything "backend-side" with a kind of "admin API" which has access to everything, and checks user roles in the backend,
18.
by trailbase 2y ago
> Edit: Based on your benchmarks repo ( https://github.com/trailbaseio/trailbase-benchmark/tree/main ...) note that compiling PocketBase with `CGO_ENABLED=1` is no longer enough to kick in the github.com&#x2
19.
by trailbase 2y ago
Back from the dead. I also now vaguely remember that there was some hiatus (probably between v0.22 and v0.23) where you took some time to rewrite the DB layer to enable custom DB drivers. Anyway, w/o fog I managed to run with mattn&#x2
20.
by trailbase 2y ago
The raw query API is an admin-only API at least for now, since SQLite doesn't have a built-in concept of row-level security. From a client's perspective it's only RESTful APIs at the moment. That said, you absolutely can gene
21.
by trailbase 2y ago
Absolutely. In terms of new clients targeting mobile teams Swift and Java/Kotlin would make the most sense. I mostly meant that even folks who code in Swift, Java and JS, would likely prefer the respective clients to be idiomatic than
22.
by trailbase 2y ago
Thanks! Happy to hear more ideas, if there's something you've always wanted :). PocketBase is great (and as I just learned, it has recently gotten even faster). One of my main goals was to expose more of the raw SQLite goodness.
23.
by trailbase 2y ago
I'm not sure if you're referencing the client libs or the server-side v8 integration. Either way, both are async. The client is async because there's network in between. And the server-side v8 integration is async to schedule
24.
by trailbase 2y ago
IIUC, what you're asking for is what it is, i.e. TrailBase is like FireBase, as opposed to a FireBase running entirely on the client. We probably both agree that ACLs enforced by the client are no protection at all. Did I misunderstand
25.
by trailbase 2y ago
You might be thinking JavaScript runs on a single threaded event loop? That's correct, however you can run N event loops in parallel (isolates in v8 lingo). `deno serve` even has a `--parallel` flag ( https://docs.deno.com&#x
26.
by trailbase 2y ago
I'm happy to report that v0.25.0 already w/o CGO driver (fighting it right now) and GOOS=linux CGO_ENABLED=0 GOAMD64=v4 improved about 35% from 61.7s per 100k inserts to about 40s :clap: I still wanna get the mattn/go-sqlite3
27.
by trailbase 2y ago
I may plea the fifth, i.e. I'm not sure what this entails but would love to hear more. Also feel free to file a feature request. Naively, I would argue that being idiomatic in the respective ecosystem is more important than perfect con
28.
by trailbase 2y ago
- It is nice to see more backends utilizing SQLite. Hey thanks for chiming it. Huge fan of PocketBase, has been a major inspiration :applause:. For anyone driving by, certainly a more mature product. - Based on your benchmarks repo it looks
29.
by trailbase 2y ago
First and foremost, PocketBase doesn't have an official client in go. There are third-party clients in many languages (more than TB for sure) but at this point I'm not sure how much it makes sense to promote it. Would it be faster
30.
by trailbase 2y ago
The C# insertion benchmark yields roughly 100000k inserts per 5.7s, so it's more like 17.5k inserts per second. A few observations: - Both benchmark driver and server are running locally on my laptop, completely saturating the machine.

More ›