Review the cutover's last reversible checkpoint
A rollback instruction needs a data boundary and enough time to execute. Identify exactly when the old environment stops being a safe destination.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
90 articles in Cloud solutions
Page 5 of 5
Review the shared dependency that can stop every workload
A central service simplifies some operations and concentrates others. Check its failure path before making it mandatory for the whole environment.
Read articleCheck what the backup does not include
A protection policy covers configured resources, not automatically the whole application. Review the missing dependencies before accepting the recovery plan.
Read articleReview the dependency shared by both regions
Geographic separation does not protect against every common failure. Look for shared configuration, identity and control paths that can disable both deployments.
Read articleRead the replacement actions before approving an infrastructure plan
A small configuration edit can replace a stateful resource. Review the proposed lifecycle effect and its data consequences, not only the changed line of code.
Read articleReview what happens when the release metrics disappear
Analysis failures are part of the rollout design. An empty or broken query must have an explicit outcome before it controls production exposure.
Read articleReview the request that never reaches the server
A backend success ratio covers only what the backend observes. Check which failures happen earlier and how the service will recognise them.
Read articleReconcile the rounded shares back to the pool
Independent rounding can make allocated totals differ from source cost. Define how residuals are handled and test the edge cases explicitly.
Read articleVerify that the old credential is actually revoked
Publishing a new value does not necessarily remove the old authority. Review the target's credential and session behaviour before declaring rotation complete.
Read articleThe migration is not finished when the window closes
Support needs the final system state, temporary exceptions and retirement conditions. Hand over the operating service, including what still remains in the old environment.
Read articleHand over the platform as a service, not a diagram
Workload teams need clear requests, support routes and change expectations. Explain how they use the foundation and who resolves problems at each boundary.
Read articleLet the next operator run the restore drill
Recovery knowledge should survive a team change. Use a fresh operator to test the runbook, access and decision points before an incident demands them.
Read articleName who can declare regional recovery
Technical signals inform the decision, but the service needs a clear authority and a usable procedure. Hand over both before the incident window.
Read articleExplain which system owns each infrastructure field
Drift often returns because two teams or controllers believe they own the same setting. Hand over those boundaries alongside the code and state location.
Read articleGive on-call staff a clear release stop control
The operator needs to know which action limits exposure, what it leaves running and how to verify the result. Hand over those details before the first automated rollout.
Read articleGive the service objective an owner who can change priorities
Reliability reporting matters when someone can act on it. Hand over the definition, response policy and authority to choose corrective work.
Read articleName the owner of the shared-cost rule
A report needs someone who can explain and change its policy. The engineer running the data pipeline should not have to settle every dispute about fairness.
Read articleHand over the consumer list with the secret reference
The next operator needs to know who uses a credential, how they refresh it and what a failed transition looks like. A secret-store location alone is not enough.
Read article