Transfer ownership of the capability, not a folder
A module owner needs responsibility for its rules, public contract, data and operational behaviour. Source-code location is only one part of that responsibility.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
100 articles in Software architecture
Page 6 of 6
Give operators an event trail they can follow
Support needs to trace a committed business change through publication and consumption. Transfer identifiers, recovery rules and ownership for every stage.
Read articleDocument what makes a command the same command
Transfer the identity, payload-equivalence and retention rules with the endpoint. Callers and operators need the same understanding of a retry.
Read articleHand over the evidence required for deprecation
The next team needs to know who still uses the old contract, what those callers depend on and which conditions allow it to be retired.
Read articleGive maintainers a map of partially completed states
Operators need to know which effects exist, which remain uncertain and who can resolve them. Transfer that map with the coordinator code.
Read articleGive support a tenant-safe diagnostic path
Operators should be able to locate a failure without gaining unnecessary access to every customer's data. Transfer scoped tools and escalation rules with the application.
Read articleName the owner of an event's meaning
The platform team can run the broker, but domain teams must resolve what published facts mean. Make that responsibility visible before a disputed change reaches production.
Read articleDocument how to bypass the cache safely
The receiving team needs a way to inspect authoritative data and recover stale entries without turning a diagnostic action into a production outage.
Read articleHand over the migration's unfinished state explicitly
A paused backfill or retained old column is part of the running system. Give the next team the evidence and authority to finish it safely.
Read articleExplain the invariant before the locking code
A maintainer can preserve the wrong lock and still break the system. Hand over the business rule, every writer that protects it and the evidence that it holds.
Read article