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 226 archive entries
Page 2 of 10
Release-ready engineering: 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 the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: 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 the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: 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 how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Customer identity across systems
Identity resolution is the foundation of a coherent customer view across Salesforce and connected platforms. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: 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 how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: 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 how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteProtecting the data contract: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Customer identity across systems
Identity resolution is the foundation of a coherent customer view across Salesforce and connected platforms. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteObservability before production: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily note