Salesforce daily archive
730 days of practical thinking.
One retrospective note for every day from 2 September 2024 to 1 September 2026.
Archive dates organise the subject history. They do not claim the notes were originally published on those dates.
Showing 113 archive entries
Page 4 of 5
Recognising the anti-pattern: API boundaries
An API should expose a stable business capability rather than mirror a database or a single user interface. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Customer identity across systems
Identity resolution is the foundation of a coherent customer view across Salesforce and connected platforms. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Master data decisions
A connected estate needs a clear answer to which system is authoritative for each important business fact. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Synchronous or asynchronous
Timing is an architectural decision: a process should wait only when the immediate response genuinely changes the next action. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteMaking team hand-offs work: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Data virtualisation
External data can sometimes remain in its source while Salesforce presents it at the point of work. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Error recovery
Failure handling is part of the business process, not a technical appendix added after the happy path. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: API boundaries
An API should expose a stable business capability rather than mirror a database or a single user interface. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Customer identity across systems
Identity resolution is the foundation of a coherent customer view across Salesforce and connected platforms. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Master data decisions
A connected estate needs a clear answer to which system is authoritative for each important business fact. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Synchronous or asynchronous
Timing is an architectural decision: a process should wait only when the immediate response genuinely changes the next action. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteGovernance without gridlock: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Data virtualisation
External data can sometimes remain in its source while Salesforce presents it at the point of work. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Error recovery
Failure handling is part of the business process, not a technical appendix added after the happy path. This retrospective daily note considers how to create control without slowing every useful change.
Read daily note