From: | Zahir Lalani <ZahirLalani(at)oliver(dot)agency> |
---|---|
To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Framework for 0 downtime deploys |
Date: | 2021-05-22 11:11:46 |
Message-ID: | AM8PR06MB7681DA3D646174B02717AAE4A7289@AM8PR06MB7681.eurprd06.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Confidential
Hello All
I wonder if I could garner some of the wealth of experience on this group:
Our current application deployments (every 3 weeks) require about 30min downtime. We are now tasked of making this 0 downtime.
From all the reading I have done, we have solutions for the infrastructure and code deploy, but with regards to the DB the main issue seems to be keeping the new deploy backwards compatible - functions/tables/fields - all of it.
That seems like quite a large management task and would require careful reviews of changes. Is there any type of framework that already manages this type of capability? Or are there aspects of PG that we should be using in this regard?
Thx
Z
From | Date | Subject | |
---|---|---|---|
Next Message | Nikolay Samokhvalov | 2021-05-22 12:31:30 | Re: Framework for 0 downtime deploys |
Previous Message | Peter J. Holzer | 2021-05-22 10:52:43 | Re: pgbackrest - hiding the encryption password |