From: | Karl Martin Skoldebrand <KS0C77263(at)TechMahindra(dot)com> |
---|---|
To: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | SV: Databases and servers |
Date: | 2019-08-21 08:18:23 |
Message-ID: | 1566375661635.30946@TechMahindra.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
________________________________________
Från: Peter J. Holzer <hjp-pgsql(at)hjp(dot)at>
Skickat: den 20 augusti 2019 22:58
Till: pgsql-general(at)lists(dot)postgresql(dot)org
Ämne: Re: Databases and servers
On 2019-08-20 10:33:17 +0000, Karl Martin Skoldebrand wrote:
> I just discovered that a client has done this:
>
> They have two web applications A1 and A2. They have seperate hostnames/URLs.
> Both have a production and a test database A1p and A1t/ A2p and A2t.
>
> What they've done is have both A1p and A2p on the same actual databaser server
> and A1t and A2t on the same server.
>
> So, I'm thinking - if a bug in application A1 crashes the application and
> database badly it will risk bringing down both services A1 and A2. The same
> risk would be evident on a successful security breach.
>
> I would prefer to A1p and A2p on seperate servers, maybe keeping A1t and A2t on
> the same. (This is what seems to be happening when the database servers are
> being repladed).
On rereading this I notice that I'm not sure what that means. If you
propose replacing the two servers with three (two production, one test)
or even four (two production and two test), I agree.
===
I was proposing replacing the two servers with three (or four). Running production on two seperate servers and possibly the tests on one (or possibly two servers).
/M.
============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Olarte | 2019-08-21 09:35:53 | Re: SELECT all the rows where id is children of other node. |
Previous Message | Karl Martin Skoldebrand | 2019-08-21 08:11:25 | SV: Databases and servers |