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 10 of 10
Designing for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily note