News for hackers. Stuff that matters.
Re:Optimizing SQLite for Servers by tiffanyh on Thursday February 15, 2024 @05:00PM (#39389681)
I'm surprised they didn't spend more time talking about HCTree branch.

https://sqlite.org/hctree/doc/hctree/doc/hctree/index.html

Re:Optimizing SQLite for Servers by phi-go on Friday February 16, 2024 @02:53AM (#39394360)
That branch seems to be a prototype.
Re:Optimizing SQLite for Servers by neverrroot on Thursday February 15, 2024 @06:16PM (#39390641)
We need more sqlite on the servers. Much more.
Re:Optimizing SQLite for Servers by awskinda on Thursday February 15, 2024 @09:44PM (#39392514)
Why?
Re:Optimizing SQLite for Servers by foofie on Friday February 16, 2024 @01:48AM (#39394004)
Systems are simpler, and not requiring a network connection also makes them more performant.
Re:Optimizing SQLite for Servers by jbverschoor on Friday February 16, 2024 @05:33PM (#39403898)
You can /should use sockets with ppstgresql, and even your backend (app server).
Re:Optimizing SQLite for Servers by neverrroot on Friday February 16, 2024 @02:41AM (#39394294)
Because of its simplicity and its stability. And it’s absolutely capable of replacing many “traditional” RDBMs from a performance perspective or data size capability standpoint.

I’m not claiming that sqlite is capable of delivering high performance on par, the reason is that so many applications don’t need more performance that what sqlite is capable of.

Re:Optimizing SQLite for Servers by giovannibonetti on Thursday February 15, 2024 @08:18PM (#39391819)
Related: Turbo [1] helps dealing with SQLite replication in a different way.

[1] https://turso.tech/

Re:Optimizing SQLite for Servers by ghaering on Friday February 16, 2024 @01:30AM (#39393883)
For production setups, you usually want high-availability. So unless you use it on a network file system like EFS (which the SQLite author recommends against), SQLite is not an option.
Re:Optimizing SQLite for Servers by neverrroot on Friday February 16, 2024 @02:52AM (#39394356)
If HA is what you need, there are solutions.

But it just so happens that I’ve seen in the real world so many single instances of Oracle, PostgreSQL, Maria/MySQL, SQL Server etc. that I know in practice there is a big difference between what someone needs/wants and what someone gets.

A lot of that has also to do with the complexity of setting up HA instances of such databases. Also this is simpler with HA sqlite setups.

Re:Optimizing SQLite for Servers by yellowapple on Friday February 16, 2024 @08:56PM (#39405559)
In most cases, primary/failover is more than enough for high availability - and things like LiteFS are able to provide that for SQLite.
Re:Optimizing SQLite for Servers by citrin_ru on Saturday February 17, 2024 @06:59AM (#39408680)
Not all production setups require >99.999% availability. There are many cases when it’s OK to use a VM with periodic snapshots/backups. In case of a HW failure (which doesn’t happen often) you can recover from a snapshot. An advantage is than an app with a DB in a file (no HA) requires almost no maintenance work.