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 37 archive entries
Page 1 of 2
Failure-first thinking: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteA practical architecture review: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteThe decision before the tool: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily note