From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aljosha Papsch Subject: Re: postgresql vs sqlite for Cuirass (was Re: Hackathon: Mumi and Cuirass) Date: Fri, 17 May 2019 12:42:55 +0200 Message-ID: References: <875zqrgqlf.fsf@elephly.net> <20190506225554.43e93d0d@alma-ubu> <87imuabhsw.fsf@roquette.mug.biscuolo.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-8DUA2szzAZ9MWMqXihhP" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:53181) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRaKN-0001yi-44 for guix-devel@gnu.org; Fri, 17 May 2019 06:43:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hRaKM-0005Pc-5R for guix-devel@gnu.org; Fri, 17 May 2019 06:43:03 -0400 Received: from dedi718.your-server.de ([78.46.1.118]:57220) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hRaKL-0005JU-VH for guix-devel@gnu.org; Fri, 17 May 2019 06:43:02 -0400 Received: from [78.46.172.3] (helo=sslproxy06.your-server.de) by dedi718.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1hRaKG-0003uz-9V for guix-devel@gnu.org; Fri, 17 May 2019 12:42:56 +0200 Received: from [80.146.188.122] (helo=pc-apapsch) by sslproxy06.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1hRaKG-000VkV-5B for guix-devel@gnu.org; Fri, 17 May 2019 12:42:56 +0200 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org --=-8DUA2szzAZ9MWMqXihhP Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Am Freitag, den 17.05.2019, 10:26 +0200 schrieb G=C3=A1bor Boskovits: > Any suggestions to overcome this would be appreciated. I would go with the client/server database. It helps scaling in the long term and Guix must take over the world, no? With SQLite you'll be stuck with the single file on a single server. You could implement your custom replication using rsync or whatever, but you'll have to ensure that the receivers do not write to the file (readonly "slaves"). In the end it will be a problem already solved by Postgres and other server/client databases. I don't know about multi-master replication in Postgres, with MySQL it would be possible. > 200 SQL statements per webpage is excessive for client/server > database like MySQL [...] But with SQLite [it's] not a problem. The main problem the author sees is the roundtrip of the message to the DB server. It's a common problem that you will get into when moving from single machine to cluster. IMHO you shouldn't shy away by sticking to the single machine, but optimize the application to get the benefits that a cluster provides you (mainly availability). Best regards Aljosha (checking Guix out for web development) --=-8DUA2szzAZ9MWMqXihhP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEocWRw6YDkdbMtdYEuRboHNjXgkUFAlzekC8ACgkQuRboHNjX gkWj8gf/Vwmu5QLSqaWlh8maHbOnEzEypw50eW8rN93velYruldvIuYO1hbiReop JNR/l5d6Z/3bWMui4nltW+P6k9Pubz7miH8Bqf+jujutMgFf2ZtSexIKjd1Lyy5g hxZcTIldft8lQAONfxQOmTXRC+i/tZ0TahcfvDTHxnPtr1u8iU/gZX2cXQQ33dkC nUn/XNijX65gEyuPvUXqdHiNymhd58SFtju03FOo2es8L5XLnQArqj+66tCzXwRF XBqLzauVKfDj3vt0QCn1h7YDh19g0hekecbdAY75LyJCzFTBBcOAO2fUMwHSq8bM yWOftVBwbjpy64IaLN375I64XpZ+ug== =kcJ9 -----END PGP SIGNATURE----- --=-8DUA2szzAZ9MWMqXihhP--