Date: Wed, 29 Apr 2026 15:42:31 +1000
From: Guyren Howe <guyren@gmail.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>, PostgreSQL General
 <pgsql-general@postgresql.org>
Message-ID: <39f640d6-2a39-48c2-90b0-4adffe63bfc7@Spark>
In-Reply-To: <ea9ee41bb180e4cda1ad782c164a98000f49ba89.camel@cybertec.at>
References: <4237964E-B88B-4F6B-AD3D-FD67C17ED480@relevantlogic.com>
 <ea9ee41bb180e4cda1ad782c164a98000f49ba89.camel@cybertec.at>
Subject: Re: Describing the natural architecture for an internet-facing
 Postgres based app: feedback sought
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="69f19a4c_ce19105_29b7"
Archived-At: <https://www.postgresql.org/message-id/39f640d6-2a39-48c2-90b0-4adffe63bfc7%40Spark>
Precedence: bulk

--69f19a4c_ce19105_29b7
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Thanks for the feedback.

If you=E2=80=99re doing a small business application, running code in the=
 database isn=E2=80=99t a concern.

If you=E2=80=99re doing a larger application, you=E2=80=99re probably sha=
rding anyway. If you have more database servers and fewer web servers, is=
 that actually an issue=3F

Updated the piece to discuss this.
On 28 Apr 2026 at 15:20 +1000, Laurenz Albe <laurenz.albe=40cybertec.at>,=
 wrote:
> On Tue, 2026-04-28 at 13:24 +1000, guyren=40relevantlogic.com wrote:
> > Coming from a Rails/PHP/etc world. All of those communities generally=
 hold that
> > the database should be treated as a dumb data bucket with all the log=
ic in the middleware.
> >
> > I=E2=80=99ve long thought someone should write up what the alternativ=
e architecture using
> > Postgres to its fullest would look like. In order to differentiate it=
, I start from
> > the security advantages and work forward.
> >
> > I=E2=80=99d love to get some feedback on it. Harsh criticism is most =
useful=E2=80=A6 :-)
>
> No harsh critizism, but I am wary of all extremist positions.
> Just as I think that it is silly to keep the database as dumb as possib=
le,
> I doubt that it is a good position to put all the smarts into the datab=
ase.
>
> One obvious disadvantage is that if you put much of the processing into=

> the database, most of the load will be on the database server, which is=

> difficult to scale.
>
> Why not let each component do what it is best at=3F
>
> Yours,
> Laurenz Albe

--69f19a4c_ce19105_29b7
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22>
<div>Thanks for the feedback.</div>
<div>&=23160;</div>
<div>If you=E2=80=99re doing a small business application, running code i=
n the database isn=E2=80=99t a concern.</div>
<div>&=23160;</div>
<div>If you=E2=80=99re doing a larger application, you=E2=80=99re probabl=
y sharding anyway. If you have more database servers and fewer web server=
s, is that actually an issue=3F</div>
<div>&=23160;</div>
<div>Updated the piece to discuss this.</div>
</div>
<div name=3D=22messageReplySection=22>On 28 Apr 2026 at 15:20 +1000, Laur=
enz Albe &lt;laurenz.albe=40cybertec.at&gt;, wrote:<br />
<blockquote type=3D=22cite=22>On Tue, 2026-04-28 at 13:24 +1000, guyren=40=
relevantlogic.com wrote:<br />
<blockquote type=3D=22cite=22 style=3D=22border-left-color: grey; border-=
left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left:=
 10px;=22>Coming from a Rails/PHP/etc world. All of those communities gen=
erally hold that<br />
the database should be treated as a dumb data bucket with all the logic i=
n the middleware.<br />
<br />
I=E2=80=99ve long thought someone should write up what the alternative ar=
chitecture using<br />
Postgres to its fullest would look like. In order to differentiate it, I =
start from<br />
the security advantages and work forward.<br />
<br />
I=E2=80=99d love to get some feedback on it. Harsh criticism is most usef=
ul=E2=80=A6 :-)<br /></blockquote>
<br />
No harsh critizism, but I am wary of all extremist positions.<br />
Just as I think that it is silly to keep the database as dumb as possible=
,<br />
I doubt that it is a good position to put all the smarts into the databas=
e.<br />
<br />
One obvious disadvantage is that if you put much of the processing into<b=
r />
the database, most of the load will be on the database server, which is<b=
r />
difficult to scale.<br />
<br />
Why not let each component do what it is best at=3F<br />
<br />
Yours,<br />
Laurenz Albe<br /></blockquote>
</div>
</body>
</html>

--69f19a4c_ce19105_29b7--