A cloud cutover needs one clear writer
Moving traffic is only part of a migration. Decide where new business changes are accepted and how that authority moves without creating conflicting histories.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
90 articles in Cloud solutions
Page 1 of 5
Build a cloud foundation teams can actually use
A landing zone should make safe deployment routine. Define ownership, identity and operating boundaries before adding shared services that every workload must depend on.
Read articleThe backup exists. Can the application use it?
A restore is complete when a verified business workflow works again. Recovering files alone does not restore identity, configuration or external dependencies.
Read articleRegional failover fails when identity stays behind
A second application region is not a complete recovery path. Authentication, keys, integrations and write ownership need the same rehearsal as compute and data.
Read articleAn emergency cloud fix needs a path back into code
Infrastructure drift is a difference to investigate, not an instruction to overwrite production. Establish why the live state changed before choosing what the next deployment should do.
Read articleA canary needs a decision, not just a traffic percentage
Sending a few requests to a new release limits initial exposure. It becomes a useful safety mechanism only when evidence determines whether to continue, pause or recover.
Read articleMeasure whether people can finish the task
A service indicator should describe the experience the application is meant to provide. CPU usage and healthy processes help explain failures, but do not establish that a task succeeded.
Read articleShared cloud spend needs a rule someone can explain
Cost allocation helps teams make decisions when they understand direct charges, shared services and adjustments. Extra decimal places do not make an arbitrary split more accurate.
Read articleRotation finishes when consumers stop using the old credential
Updating a secret store is one step in a distributed change. The target service and every consumer must agree on which credential works before the old one is retired.
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 article