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 76 archive entries
Page 4 of 4
Adoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily note