Review the read that follows a successful write
Users expect to see the change they just saved. Check the whole response path before accepting a cache policy that can return the previous value immediately afterwards.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
512 articles
Page 25 of 29
Check the SQL the migration tool will actually execute
A short ORM change can generate a costly or incompatible database operation. Review the emitted SQL and its production consequences before approval.
Read articleA retry must repeat the decision, not only the last statement
When a transaction aborts, its earlier reads may no longer be valid. Recompute the protected operation and keep irreversible effects out of the retry block.
Read articleReview 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 articleReview 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 articleReview the match before accepting a Xero reconciliation
A similar amount or document number can identify a candidate, but not always the correct resource. Establish the evidence required to confirm the relationship.
Read articleReview a cleared CRM field separately from a missing one
A partial response and an intentional removal can look similar after mapping. Preserve the distinction before constructing the destination update.
Read articleReview the code between persistence and acknowledgement
The receiver's success response creates a delivery promise. Check that no process crash can leave acknowledged work without a durable recovery path.
Read articleReview the retry budget across every layer
A bounded loop is not enough when several layers retry independently. Count the maximum downstream attempts and keep one policy responsible for the operation.
Read articleCheck whether redrive changes the identity used for deduplication
Transport tools may assign new metadata during recovery. Verify that the application still recognises the original business operation.
Read articleReview dates, instants and durations as different data types
A calendar date, a local appointment and an elapsed interval answer different questions. Converting them all to timestamps can change their meaning.
Read article