> Correct. It’s a tragically wrong piece of folk wisdom that’s pretty general across web development communities.
So, what's your advice, and is there some book / resource to get upto speed?
Thanks!
On Tue, Jun 27, 2023 at 10:38 AM Guyren Howe <guyren@gmail.com> wrote:
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.
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.