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 1 of 10
Performance with purpose: Data virtualisation
External data can sometimes remain in its source while Salesforce presents it at the point of work. This retrospective daily note considers where latency and throughput genuinely affect the business journey.
Read daily notePerformance with purpose: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers where latency and throughput genuinely affect the business journey.
Read daily notePerformance with purpose: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers where latency and throughput genuinely affect the business journey.
Read daily notePerformance with purpose: Error recovery
Failure handling is part of the business process, not a technical appendix added after the happy path. This retrospective daily note considers where latency and throughput genuinely affect the business journey.
Read daily notePerformance with purpose: 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 where latency and throughput genuinely affect the business journey.
Read daily notePerformance with purpose: Customer identity across systems
Identity resolution is the foundation of a coherent customer view across Salesforce and connected platforms. This retrospective daily note considers where latency and throughput genuinely affect the business journey.
Read daily notePerformance with purpose: 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 where latency and throughput genuinely affect the business journey.
Read daily notePerformance with purpose: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers where latency and throughput genuinely affect the business journey.
Read daily notePerformance with purpose: 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 where latency and throughput genuinely affect the business journey.
Read daily notePerformance with purpose: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers where latency and throughput genuinely affect the business journey.
Read daily noteTesting the business outcome: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteRelease-ready engineering: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily note