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 113 archive entries
Page 1 of 5
Adoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteDesigning for maintainability: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: 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 another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: 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 another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: 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 another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: 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 another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: 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 another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: 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 another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteThe cost of complexity: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: 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 unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: 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 unnecessary components and customisation create recurring operating cost.
Read daily note