From: Guyren Howe <guyren@gmail.com>
Cc: B M <bmmasprep@gmail.com>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>
Subject: Re: Large scale reliable software system
Date: Mon, 26 Jun 2023 22:07:53 -0700
Message-ID: <411C8CAC-D442-4CC8-B952-455B4CCC6A02@gmail.com> (raw)
In-Reply-To: <CAOzAquLteiSn2Nt1ngNriuBkH4GhkGfcUyyTymYm5MkNMTG2YQ@mail.gmail.com>
References: <CAPDsptUFi483wbYfGYvs8PmBC=CqC+SMNJ4yXY+8L=MV89YY5g@mail.gmail.com>
<32335c82-61cf-2ad9-e232-d3946adb7056@aklaver.com>
<3b9e3f40-61aa-431a-a610-472ca8205e36@Spark>
<CAOzAquLteiSn2Nt1ngNriuBkH4GhkGfcUyyTymYm5MkNMTG2YQ@mail.gmail.com>
Correct. It’s a tragically wrong piece of folk wisdom that’s 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 PM 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
>>
>>
>>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: guyren@gmail.com, bmmasprep@gmail.com, adrian.klaver@aklaver.com
Subject: Re: Large scale reliable software system
In-Reply-To: <411C8CAC-D442-4CC8-B952-455B4CCC6A02@gmail.com>
References: <CAPDsptUFi483wbYfGYvs8PmBC=CqC+SMNJ4yXY+8L=MV89YY5g@mail.gmail.com> <32335c82-61cf-2ad9-e232-d3946adb7056@aklaver.com> <3b9e3f40-61aa-431a-a610-472ca8205e36@Spark> <CAOzAquLteiSn2Nt1ngNriuBkH4GhkGfcUyyTymYm5MkNMTG2YQ@mail.gmail.com> <411C8CAC-D442-4CC8-B952-455B4CCC6A02@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox