Map each committed effect before defining its compensation
Design the recovery record from the actual side effects. A list of service calls does not tell the coordinator what can safely be corrected after failure.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
512 articles
Page 5 of 29
Carry tenant identity into queued work
A worker needs an explicit, trusted scope for the job it executes. Save that scope at submission and validate it again according to the workflow's authority policy.
Read articleDefine whether the event is a snapshot or a change
Build an event contract around one interpretation. A consumer needs to know whether it should replace a view, apply a transition or fetch more information.
Read articleMake cache keys describe the result they contain
Include every input that changes a cached response. A resource identifier alone is rarely enough for tenant data, translations or filtered views.
Read articleBackfill without overwriting a newer edit
A migration worker and a live request can touch the same row. Make the update conditional on the state the worker actually read.
Read articleReject an edit based on an old revision
Carry the version a user actually edited into the save request. Compare it atomically with the current record before replacing data.
Read articleStop background writers before the final data sync
A quiet website can still have an active database. Include jobs, callbacks and queued work in the cutover fence.
Read articleProvision one workload environment from a reviewed definition
Make the first environment reproducible before scaling account creation. Include the access, logging and ownership that turn empty infrastructure into a usable workspace.
Read articleRestore into an isolated environment before reconnecting integrations
Build the recovery environment so the application can be tested without repeating production side effects. Reconnect dependencies deliberately after data verification.
Read articlePrepare recovery dependencies before the outage
Reduce the work that must happen under incident pressure. Keep the target's required artefacts, authority and configuration ready through the normal release process.
Read articleAdd a read-only drift check to the delivery workflow
Detect changes without automatically applying a correction. Give the owning team a useful difference and enough context to decide what should happen.
Read articleSeparate release identity from feature exposure
Deploying code and enabling behaviour are related but different actions. Track both so an operator can tell what a request actually experienced.
Read articleCount accepted jobs that miss their completion deadline
Queue workers can look healthy while old work remains unfinished. Measure from acceptance to the required result, including jobs that never emit a completion event.
Read articlePreserve source charges before applying ownership rules
Keep raw billing facts separate from derived allocation. This makes corrections and historical reporting possible without repeatedly reinterpreting the original data.
Read articleGive consumers a defined secret-refresh path
A credential loaded once at startup will not automatically follow rotation. Make refresh behaviour explicit and test it at the connection boundary.
Read articleSave the integration intent before sending it to Xero
A durable operation record gives retries and support a shared source of truth. Record the target organisation and expected request before making the external call.
Read articleEncode the field policy beside the mapping
Keep direction, authority and empty-value behaviour in one reviewed definition. Scattered conditionals make the same field behave differently across imports and live updates.
Read articlePut a durable inbox behind the webhook endpoint
Store verified event identity and processing state before returning success. Let workers handle slow business logic without losing the ability to retry.
Read article