Re: What is the best setup for distributed and fault-tolerant PG database?

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: What is the best setup for distributed and fault-tolerant PG database?
Date: 2023-01-04 23:54:03
Message-ID: 547a49b4-c296-b82f-df34-11cc819d4336@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/4/23 06:26, Age Apache wrote:
> Dear PG experts,
>
> I am new to postgres, and I am also not a DBA. I am a solo developer
> who is trying to evaluate what database to use for my hybrid
> multi-tenancy sub-apps i.e. users of the application will be
> authorised to use part or whole of the application based on their
> authorisation levels. This delineation of user access has to also be
> supported by the database, if possible. Also, for audit purposes the
> data is append only. And the design is based on just two
> tables(vertices and edges) to emulate a document-oriented(jsonb) graph
> structure.
>
> Postgres is the database I am leaning towards for this project. But as
> I am not a DBA and also a solo developer, I am trying to understand
> how I can spend less time managing the DB and more time developing the
> application. I would like to have a distributed and fault-tolerant DB
> setup with multiple read and write nodes with little to no
> configuration on my part, if possible. I am looking for a self-hosted
> open source solution.
>
> Is this possible with PG? What is the best way to achieve this for a
> non-DBA solo developer like me?
>
> Thanks and kind regards
None of the experts chimed in so I ante up my $0.02.

It won't be possible unless you become a serious DBA _and_ solo (full
stack) developer.  Or you pay for db support.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Saul Perdomo 2023-01-05 03:34:11 Re: What is the best setup for distributed and fault-tolerant PG database?
Previous Message Rébeli-Szabó Tamás 2023-01-04 21:52:27 Re: curious postgres (crash) recovery behavior