Distributed SQLite: Paradigm shift or hype?
kerkour.com
Distributed SQLite: Paradigm shift or hype?
1–10 of 165 posts
Re: Distributed SQLite: Paradigm shift or hype?
#2See some development frameworks for local-first apps support both SQLite and PostgreSQL. The advantage of using PostgreSQL is that when you add a cloud option to your local-first app, the migration becomes much easier.
Re: Distributed SQLite: Paradigm shift or hype?
#3This is kind of missing the point. I can only speak for the company that sponsors LiteFS (I don't think any edge computing companies put 'otoolep up to doing rqlite, for instance). We love Postgres. Most of our users use Postgres. And Postgres works fine in edge/backhaul configurations; companies were doing geographically distributed Postgres read replicas long, long before we came around. That's where we got the idea.
The idea of LiteFS is:
* Most apps are read-heavy, and some of them are overwhelmingly read-heavy.
* If you're read-heavy and can thus get away with it, there's a pretty significant performance win in replacing the networked n-tier architecture with SQLite, because Postgres round trips add up over the lifecycle of any given request.
* In fact, that's so much the case that --- as Richard Hipp has been pointing out for over a decade --- you can blow off the N+1 problem and just write natural queries.
I think Ben Johnson would be the first to tell you that LiteFS isn't a perfect fit for every application. We have systems that use both Postgres and LiteFS.
Meanwhile, you have to dig to find it on our web page! It's an open source project that works everywhere Linux does. Dial back the cynicism a bit! :)
A plug here for:
https://kerkour.com/sqlite-for-servers
Same author, and one of the best SQLite articles ever.
Re: Distributed SQLite: Paradigm shift or hype?
#4this page just says 'Forbidden'
Re: Distributed SQLite: Paradigm shift or hype?
#5this page just says 'Forbidden'
I updated Chrome and reloaded.
Re: Distributed SQLite: Paradigm shift or hype?
#6"Something went wrong! Try reloading the page. If the problem persists, please update your web browser to the latest version."
RIP website.
edit: it's back
Re: Distributed SQLite: Paradigm shift or hype?
#7"Something went wrong! Try reloading the page. If the problem persists, please update your web browser to the latest version." RIP website. edit: it's back
[deleted]
Re: Distributed SQLite: Paradigm shift or hype?
#8I think this skips one mega benefit for apps.
I’ve been using liteFS in production for a couple months.
Your web app is able to resolve db queries instantly.
You don’t need loading states if you’re using complex charts and other frontend JS that waits for data.
All the data is resolved so fast and you can just return all your data like more traditional apps, and the load times are insane.
If you’re multi region you can deploy one app instance there. Instead of 2-3. Postgres read replica, maybe something like redis.
It really replaces both of those, assuming you have a read heavy app it works great.
Re: Distributed SQLite: Paradigm shift or hype?
#9"Something went wrong! Try reloading the page. If the problem persists, please update your web browser to the latest version." RIP website. edit: it's back
Should have used SQLite.
Re: Distributed SQLite: Paradigm shift or hype?
#10Among the various free backend hosting options currently available, does Cloudflare stand out as the best choice with its offerings such as Workers and D1? I would love to hear users experiences with these services or if there any informative resources that discuss the costs associated with scaling applications on the infra?