large scale reliable software system

On 6/21/23 12:52 PM, 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.

This mailing list is to discuss issues related to the PostgreSQL
documentation, not system design. There are some other places you can
have this discussion[1]https://www.postgresql.org/support/ (such as pgsql-general@), though many of the
questions you have are generally broad topics that turn into very deep,
detailed conversations.

Thanks,

Jonathan

[1]: https://www.postgresql.org/support/

I recommend posting this to pgsql-admin or pgsql-general instead of pgsql-docs
to get more responses. Besides that, pgsql-docs is for discussions on the
Postgres docs.

On 21/06/2023 18:52 CEST B M <bmmasprep@gmail.com> wrote:

I would like to know your advices to develop a large scale reliable software
system using PostgreSQL in the back-end,

This is very general but the following points hopefully lead you in the right
direction:

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

The OWASP Cheat Sheets give advice on securing web applications:
https://cheatsheetseries.owasp.org/

and performance, achieve fast response,

My general advice: design and implement for correctness, then measure and
optimize. For performance, look into high availability:
https://www.postgresql.org/docs/current/high-availability.html

make backups and save the stored data from loss.

Use pgBackRest or pgbarman with WAL streaming to reduce the recovery point
objective (the maximum period in which data might be lost).

The system will be hosted on a cloud.

Some cloud providers offer Postgres instances including backups, e.g. Google
Cloud Platform which I'm looking into right now.

--
Erik

Thank you all. I will follow your advices and directions

On Wed, Jun 21, 2023 at 7:17 PM Erik Wienhold <ewie@ewie.name> wrote: