postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuirass)

[Giovanni Biscuolo <g@xelera.eu>]

[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]

Hello Björn,

Björn Höfling <bjoern.hoefling@bjoernhoefling.de> writes:

[...]

>> 2) Cuirass
>
> On Guix days, we discussed the idea of using Postgresql as a backend.

Please do you remember the rationale behind this idea?

What is the issue with using sqlite?

Why a client/server approach vs an embedded database?

I don't have much experience with web applications backed by sqlite, but
AFAIU sqlite is sometime "misunderstood"

Some interesting arguments from sqlite developer:
https://sqlite.org/whentouse.html#website
--8<---------------cut here---------------start------------->8---

Dynamic content uses about 200 SQL statements per webpage. This setup
runs on a single VM that shares a physical server with 23 others and yet
still keeps the load average below 0.1 most of the time.

--8<---------------cut here---------------end--------------->8---

https://sqlite.org/np1queryprob.html
--8<---------------cut here---------------start------------->8---

200 SQL statements per webpage is excessive for client/server database
engines like MySQL, PostgreSQL, or SQL Server.

But with SQLite, 200 or more SQL statement per webpage is not a problem.

SQLite can also do large and complex queries efficiently, just like
client/server databases. But SQLite can do many smaller queries
efficiently too. Application developers can use whichever technique
works best for the task at hand.

[...]

N+1 Queries Are Not A Problem With SQLite

--8<---------------cut here---------------end--------------->8---

[...]

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]