The database committed. Did the event leave?
A business write and a message publish can fail independently. Save the intention to publish in the same transaction as the business change, then deliver it through a recoverable worker.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
512 articles
Page 2 of 29
A retry should not create a second business action
When a response is lost, the caller needs a way to repeat the request without repeating its effect. Give the intended action an identity that survives every attempt.
Read articleChange an API without stranding its existing clients
Compatibility includes behaviour, defaults and error handling as well as field names. Review what older callers rely on before changing the contract.
Read articleCompensation is a business action, not a database undo
A distributed workflow cannot usually erase every completed step. Define the corrective business action for each effect and make unresolved states visible.
Read articleTenant isolation must survive background work
Filtering an API request by organisation is not enough if jobs, caches or exports lose that context. Carry the boundary through every path that reads or changes tenant data.
Read articleEvents need a meaning that survives new consumers
A message can remain valid JSON while its meaning changes. Define the business fact, its timing and its replay behaviour before other systems depend on it.
Read articleA cache needs a freshness promise
Decide how old a value may be and what happens when that limit is exceeded. Faster reads are useful only while the result remains suitable for the task.
Read articleA database migration has to support two application versions
During a rolling release, old and new code share the database. Design the transition around that overlap before removing or reinterpreting stored data.
Read articleTwo valid requests can still produce an invalid result
Concurrency control protects the rule shared requests depend on. Start with that rule, then choose conditional writes, locks or transaction isolation to enforce it.
Read articleA 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 articleBuild 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 article