Rehearse rollback after the target accepts a write
The difficult recovery case begins when the new environment contains data the old one does not. Test that boundary explicitly.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
90 articles in Cloud solutions
Page 2 of 5
Test a denied deployment before a team needs an exception
A platform control should fail clearly and preserve a usable recovery path. Exercise both legitimate restrictions and accidental policy conflicts.
Read articleRestore a point before the bad change
Recovery from corruption requires more than choosing the newest backup. Rehearse how to identify a clean point and account for legitimate work after it.
Read articleSimulate a network partition, not only a stopped server
The harder failover case is an old region that some clients can still reach. Test how the design prevents conflicting writes under partial visibility.
Read articleChange one safe resource outside the deployment pipeline
A controlled drift exercise should prove detection, investigation and reconciliation. Stopping at an alert leaves the most consequential part untested.
Read articleMake the canary fail before trusting automatic promotion
Test the release controller with bad results, missing results and a healthy control group. The exercise should prove the decision path, not just deployment mechanics.
Read articleBreak the workflow while leaving the health endpoint green
A controlled dependency failure can show whether monitoring detects user impact or only process availability.
Read articleRemove an ownership tag and follow the charge
Missing metadata should produce visible unresolved cost. Test that it does not disappear from totals or get silently assigned to the wrong team.
Read articleKeep one worker on the old credential during the drill
A delayed consumer reveals whether rotation depends on every process updating at once. Test its recovery after the previous credential is no longer usable.
Read articleProve the workflow after the traffic switch
Healthy instances and low error rates do not show that customers can finish their work. Define cutover checks around complete business outcomes.
Read articleMeasure the time from environment request to working deployment
Account creation speed misses much of the work. Track when a team can deploy, diagnose and operate a real service through the supported path.
Read articleTime recovery until the business task works
Infrastructure restore duration is only part of recovery time. Include access, configuration, validation and the return of the required workflow.
Read articleMeasure recovery at the user's endpoint
A successful regional promotion does not show when clients can work again. Include routing, authentication and data correctness in the recovery result.
Read articleMeasure how long important drift remains unexplained
A count of differences mixes harmless metadata with serious exposure. Track ownership, consequence and resolution time to understand whether the process works.
Read articleA quiet canary is not evidence of a healthy release
Promotion needs relevant observations as well as a low error rate. Show the request count, workload mix and observation window behind the decision.
Read articleDefine the denominator before agreeing on reliability
A percentage can change dramatically when failed attempts are excluded. Agree what counts as an eligible operation and keep that definition stable enough to compare results.
Read articleReport allocation coverage without hiding the unknowns
Coverage is useful only when unresolved and centrally funded costs remain visible. A forced assignment can improve the percentage while making the report less trustworthy.
Read articleTrack credential adoption, not only rotation-job success
A completed automation run does not show that every consumer moved. Measure target validity, consumer refresh and retirement of the previous authority separately.
Read article