111–120 of 211 posts
I'm a huge fan of Pocketbase. Backing up the sqlite though had me more stressed than I'd prefer, and I wanted a plug-and-play way to sqlite3_rsync a backup while Pocketbase was running: so I've been working on this: https://sqlrsync.com . MVP works. Billing isn't being checked yet (be gentle but it's Cloudflare Durable Objects underneath so it should be local, fast, and resilient.) Would love feedback from anyone ope…
Beware of pocketbase! I am running my startup wetarseel.ai. You'll be badly locked into one instance with one sqlite file, plus its queries are not mapping to SQL, try a bulk delete and it will choke your entire system, plus other footguns.
Sounds like an sqllite performance tuning issue than anything else.
Earlier quoted context omitted.
How do you use simple SQLite without any code in a webapp where the database is on the server?
You can't. I am curious if this adds another layer of latency.
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 for JS (just for the event-loop to do the IO and getting back to you).
However, if you have multiple processes reading and writing from the same DB it may actually aid latency due to congestion.
I ran some benchmarks (TrailBase author here and big fan of PocketBase): https://trailbase.io/reference/benchmarks#insertion-benchmar..., where you can see, e.g. the single-process drizzle (i.e. JS with in-process SQLite) performance vs over-HTTP for TrailBase. PocketBase should be similar when not fully loaded. There's also some concrete latency percentile numbers when at full-tilt: https://trailbase.io/reference/benchmarks#read-and-write-lat.... On my machine you can expect p50 to be around 15-20ms.
Earlier quoted context omitted.
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 –…
Really? I couldn't really see anything wrt degraded performance from my casual glance. To me, It looks like there are just best effort events with literally no constraints or handling for delays etc And again, I didn't see how you'd even implement such without being on both sides of the networked connection I guess I just have to accept that the term has lost it's meaning at this point and can be used for whatever wh…
It's maybe more like you point out: realtime in the OS context vs realtime in an event processing context. The latter is certainly not defined as strictly and often just means push-based. It has been a popular moniker, e.g. in kafka-land, for a while. I'm not sure it intrinsically takes away from the OS context - it doesn't need to be a deep dish pizza situation.
Hmmm… firebase clones are many and varied. Whats special about this one? Being a single file binary doesnt impress me; thats true of many projects in many langauges. It seems nice you can use it as a go framework if you happen to use go, but Im not really compelled by the “it doesn't scale at all” aspects of it. Someone whos used some other similar stuff comment on why this over any of the others, eg. self hosted sup…
Hmmm… firebase clones are many and varied. Can you recommend any in particular, were I wanting to migrate a project from firebase?
Beware of pocketbase! I am running my startup wetarseel.ai. You'll be badly locked into one instance with one sqlite file, plus its queries are not mapping to SQL, try a bulk delete and it will choke your entire system, plus other footguns.
I am so confused about this message Sounds like an sqllite performance tuning issue than anything else.
Hmmm… firebase clones are many and varied. Whats special about this one? Being a single file binary doesnt impress me; thats true of many projects in many langauges. It seems nice you can use it as a go framework if you happen to use go, but Im not really compelled by the “it doesn't scale at all” aspects of it. Someone whos used some other similar stuff comment on why this over any of the others, eg. self hosted sup…
Could you elaborate a bit more on your scaling concerns? You can certainly have lock-congestion with SQLite. That, said Postgres - while awesome - isn't the most horizontally scalable beast.
Hmmm… firebase clones are many and varied. Whats special about this one? Being a single file binary doesnt impress me; thats true of many projects in many langauges. It seems nice you can use it as a go framework if you happen to use go, but Im not really compelled by the “it doesn't scale at all” aspects of it. Someone whos used some other similar stuff comment on why this over any of the others, eg. self hosted sup…
One binary to manage one sqlite file is indeed quite a selling point in comparison to this: https://github.com/supabase/supabase/blob/master/docker/dock...
Not saying Supabase is bad at all at what it does and I am very glad that it exists as an open source project, but they don't target the same type of project complexity at all.
I love it and use it for personal projects and internal tools. I tend to combine it with https://pocketpages.dev/ which gives me file-based routing and nice templates. Ah, and Pocketbase has automatic database migrations, so all schema modifications can go into version control. I even hacked a Gemini protocol server into it, so that I can browse my personal knowledge graph using Lagrange.
What is Lagrange? I couldn’t find any project in the context of LLM or knowledge graph.
Beware of pocketbase! I am running my startup wetarseel.ai. You'll be badly locked into one instance with one sqlite file, plus its queries are not mapping to SQL, try a bulk delete and it will choke your entire system, plus other footguns.
I am so confused about this message Sounds like an sqllite performance tuning issue than anything else.
Naively, I would expect SQLite to be able to delete tens-of-thousands (or even hundreds) of records per seconds, since it's simply appending deletions to the WAL.