Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qE0vo-00034I-Ax for pgsql-general@arkaria.postgresql.org; Tue, 27 Jun 2023 05:08:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qE0vm-0004vM-So for pgsql-general@arkaria.postgresql.org; Tue, 27 Jun 2023 05:07:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qE0vm-0004tL-FX for pgsql-general@lists.postgresql.org; Tue, 27 Jun 2023 05:07:58 +0000 Received: from mail-vs1-xe30.google.com ([2607:f8b0:4864:20::e30]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qE0vi-000icp-J3 for pgsql-general@lists.postgresql.org; Tue, 27 Jun 2023 05:07:57 +0000 Received: by mail-vs1-xe30.google.com with SMTP id ada2fe7eead31-43f40006c48so1065693137.1 for ; Mon, 26 Jun 2023 22:07:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687842472; x=1690434472; h=references:message-id:cc:date:in-reply-to:from:subject:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=MTclqKxsx6RH5aCUSz75L7/eQGJcj8lovKdF7GT032Y=; b=NxsY75cc4ospS/+gHtpjQonGkaMfZPuiUTX+kqlmnRv6mvvi3/QgP3k6QNoOS8s87f M9Vmpc4wwRyPMOLMmsO6UW3rOcNhC5cdc6/Vjdaon3IJMo81e9kXIfwRLJiDJ/r5vnhF 15Vr+dM+GMMqrDZgiFFVbvUoq2HzR/42YyHhcnr0kAPQnPr46XaG2TSmRX1OVB9P3ccj oHvB+o5GEgbOPufBvWh2gKnlqcSqr++/0JW+hvRprbMWrDSEnht9+KPw9YeKd2vgJNtV gku9Mz6KGzCBHre81TFr3IPGX/DDUgf7rPpF9mV6b9xyQfx0dO7oSQwELXkBGKhBmrRU C18w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687842472; x=1690434472; h=references:message-id:cc:date:in-reply-to:from:subject:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=MTclqKxsx6RH5aCUSz75L7/eQGJcj8lovKdF7GT032Y=; b=C/3WKyadwHPfDkGtzXhGQceH71kl8EcoArSfR5znn9TyRl6+094sayLfdP2epRu3Ox oQToK30CH0CcW1ia+1Rcs0wH8zErv50sn02foakzH4F3xY1vLkOdfpze4uUoic+iD/nc eOCko284sQcYfFGZsRS4QGQazIx2dXsWC6X4oWPIyYae+k7D0RGxFXm36Lpqh/4NvkEH B9jzWIjJckmTfmOFbmHcHoIC2YYU19RPymQ08SVhZHXwo4b5FhFToSEt/qEqR131RsQ/ dEQyHXaqePqwqnFfIYOF1Y8W1ysW2y0zTEDyQJGTdIbrBc7tj8W8UAqsvmhzEdDCbOKO Ll9A== X-Gm-Message-State: AC+VfDxSgbL7C2U7u4pSWpG7alV/lvVWaI4aFYif3FDFEmF+MBxPQW+E KC53SWLSoeUF6QNxs0QKXWt42+2ohxQucw== X-Google-Smtp-Source: ACHHUZ5bHBtHZ0JXtA+0z3zIZ5NC3xfjkm37RtUxdGSxJ3Wq1lqMzop4YKYuSSqo7CNBXSuADlCEEg== X-Received: by 2002:a67:ff05:0:b0:440:d7d1:c483 with SMTP id v5-20020a67ff05000000b00440d7d1c483mr7284366vsp.3.1687842472216; Mon, 26 Jun 2023 22:07:52 -0700 (PDT) Received: from smtpclient.apple ([2600:8801:8600:631::11]) by smtp.gmail.com with ESMTPSA id e12-20020a65478c000000b005533dcb7586sm4345372pgs.20.2023.06.26.22.07.51 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Jun 2023 22:07:51 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_66586C09-9BC5-4EED-9CF0-02FC6D504FE1" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: Large scale reliable software system From: Guyren Howe In-Reply-To: Date: Mon, 26 Jun 2023 22:07:53 -0700 Cc: B M , "pgsql-general@lists.postgresql.org" , Adrian Klaver Message-Id: <411C8CAC-D442-4CC8-B952-455B4CCC6A02@gmail.com> References: <32335c82-61cf-2ad9-e232-d3946adb7056@aklaver.com> <3b9e3f40-61aa-431a-a610-472ca8205e36@Spark> X-Mailer: Apple Mail (2.3731.600.7) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail=_66586C09-9BC5-4EED-9CF0-02FC6D504FE1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Correct. It=E2=80=99s a tragically wrong piece of folk wisdom that=E2=80=99= s pretty general across web development communities. > On Jun 26, 2023, at 21:32, Michael Nolan wrote: >=20 > It's not just Ruby, dumb databases are preferred in projects like > WordPress, Drupal and Joomla, too. >=20 > Now, if it's because they're used to using MySQL, well maybe that's > not so hard to understand. :-) >=20 > On Mon, Jun 26, 2023 at 8:05=E2=80=AFPM Guyren Howe = wrote: >>=20 >> This is a reasonable answer, but I want to offer a caveat. >>=20 >> Likely because of the influence of the originator of Ruby on Rails, = it is close to holy writ in the web development community that the = database must be treated as a dumb data bucket and all business logic = must be implemented in the Ruby or Python or whatever back end code. >>=20 >> This heuristic is nearly always mostly wrong. >>=20 >> Guyren G Howe >> On Jun 26, 2023 at 17:48 -0700, Adrian Klaver = , wrote: >>=20 >> On 6/26/23 16:48, B M wrote: >>=20 >> Dear all, >>=20 >> After greeting, >>=20 >> I taught PostgreSQL myself and developed a small scale >> experimentalsoftware system using PostgreSQL in the back-end. >>=20 >> I would like to know your advices to develop a large scale reliable >> software system using PostgreSQL in the back-end, through which i can >> share the storage with the different system users where they login to >> the system through the web application front-end with different >> passwords and usernames , save the privacy of each user data, improve >> overall system security and performance, achieve fast response, make >> backups and save the stored data from loss. The system will be hosted = on >> a cloud. >>=20 >>=20 >> https://www.djangoproject.com/ >>=20 >>=20 >> Thank you in advance. >>=20 >>=20 >> -- >> Adrian Klaver >> adrian.klaver@aklaver.com >>=20 >>=20 >>=20 --Apple-Mail=_66586C09-9BC5-4EED-9CF0-02FC6D504FE1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Correct. = It=E2=80=99s a tragically wrong piece of folk wisdom that=E2=80=99s = pretty general across web development = communities.

On Jun 26, 2023, = at 21:32, Michael Nolan <htfoot@gmail.com> wrote:

It's not just Ruby, dumb = databases are preferred in projects like
WordPress, Drupal and = Joomla, too.

Now, if it's because they're used to using MySQL, = well maybe that's
not so hard to understand.  :-)

On Mon, = Jun 26, 2023 at 8:05=E2=80=AFPM Guyren Howe <guyren@gmail.com> = wrote:

This is a reasonable answer, but = I want to offer a caveat.

Likely because of the influence of the = originator of Ruby on Rails, it is close to holy writ in the web = development community that the database must be treated as a dumb data = bucket and all business logic must be implemented in the Ruby or Python = or whatever back end code.

This heuristic is nearly always mostly = wrong.

Guyren G Howe
On Jun 26, 2023 at 17:48 -0700, Adrian = Klaver <adrian.klaver@aklaver.com>, wrote:

On 6/26/23 = 16:48, B M wrote:

Dear all,

After greeting,

I = taught PostgreSQL myself and developed a small = scale
experimentalsoftware system using PostgreSQL in the = back-end.

I would like to know your advices to develop a large = scale reliable
software system using PostgreSQL in the back-end, = through which i can
share the storage with the different system users = where they login to
the system through the web application front-end = with different
passwords and usernames , save the privacy of each = user data, improve
overall system security and performance, achieve = fast response, make
backups and save the stored data from loss. The = system will be hosted on
a = cloud.


https://www.djangoproject.com/


Thank you in = advance.


--
Adrian = Klaver
adrian.klaver@aklaver.com




3D""= --Apple-Mail=_66586C09-9BC5-4EED-9CF0-02FC6D504FE1--