Measure consumers still using a retired event shape
A producer deployment does not finish an event migration. Track who still depends on the old contract and whether historical recovery remains possible.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
100 articles in Software architecture
Page 3 of 6
A high cache hit rate can hide stale answers
Measure freshness and user-visible correctness alongside speed. A cache that repeatedly serves the wrong value can look excellent on a performance dashboard.
Read articleCount correct rows, not just migrated rows
Progress counters can report success while conversions are incomplete or wrong. Use coverage, correctness and production impact as separate acceptance measures.
Read articleCount conflicts separately from failures
A rejected competing write may show that protection worked. Measure its user impact and recovery outcome without treating every conflict as an infrastructure incident.
Read articleTrace a production defect to the owning module
Follow the business operation and its state change before assigning the incident. Technical layers can obscure which module owns the violated rule.
Read articleReconcile the outbox with the consumer outcome
An outbox row marked published does not prove the business effect completed. Trace the event through publication, delivery and consumer state before replaying it.
Read articleResolve a command whose response was lost
Keep the original operation identity while establishing what happened. A new key can turn recovery into a second business action.
Read articleIdentify the caller behind a compatibility incident
A server can be healthy while one supported client is broken. Trace the failing contract and client behaviour before treating the incident as a general outage.
Read articleContinue a saga with one irreversible effect
When a completed step cannot be undone, stop describing recovery as rollback. Establish the remaining business options and preserve the effects already known to exist.
Read articleTrace the job that ran under the wrong account
Contain further work, preserve the job's trusted context and identify every affected artifact. A wrong-tenant job can create consequences beyond its final response.
Read articleDiagnose an event that parsed but meant the wrong thing
When records look plausible but are wrong, trace how the consumer interpreted the message. Successful deserialisation can hide a semantic change.
Read articleFind which cache is still serving the old value
Trace one response through browser, edge and application layers before clearing everything. A broad purge can hide the cause and overload the source.
Read articleA migration is waiting. Find the blocker before retrying
Repeatedly launching the same command can create more contention. Inspect the active database work and choose a controlled recovery action.
Read articleTrace a deadlock to the order of resource access
Retrying can recover one request, but repeated deadlocks need a clearer picture of which transactions acquire which resources.
Read articleExtract a service only when its boundary is ready
A deployment split turns local dependencies into network and data contracts. Inspect those dependencies before moving a module into its own process.
Read articleIntroduce an outbox without double-publishing existing changes
During migration, old direct publishing and new outbox delivery can overlap. Define which path owns each committed change and make the transition observable.
Read articleAdd idempotency without breaking older callers
New callers can supply stable keys while older clients may retry without them. Define the transition behaviour explicitly instead of pretending every request is protected immediately.
Read articlePlan the period with two API contracts
Supporting old and new clients at once requires clear translation, data semantics and retirement ownership. Treat coexistence as an operating state, not a temporary omission in the design.
Read article