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.
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@xxxxxxxxxxx>, 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@xxxxxxxxxxx
