April 10, 2026 at 12:00 am
Comments posted to this topic are about the item Acting with Confidence
April 10, 2026 at 11:16 am
Back when I had to do database deployments, we would rehearse the deployment and rollback twice, checking that we had actually achieved both.
Our approach evolved over the years. A deployment used to be a 02:00 activity with a go/no-go decision at 06:00 at the latest. Rollbacks were rare. The out-of-hours nature meant that data accumulated from 02:00 to 06:00 was minimal.
Systems were isolated, so the core revenue transactions were rarely touched.
In hindsight, we should have formalised the release to include what constituted acceptable data loss in the event of a rollback.
Over time, we switched from Big Bang deployments to deploying smaller deployments. We worked out the dependencies and how to deploy as much as possible, as independently as possible. Deployability became a design priority of our systems.
The epiphany for me was the change in mindset within the organisation.
You have to design for the outcomes you want, whether that is testability, deployability, securability, observability or something else entirely.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply