The integration catalogue nobody reads
Patterns only help if people find them before inventing a new one.
3,000 mThe architecture
For architects and anyone who draws boxes for a living, Salesforce or otherwise.
This is where the diagrams live: integration, data, security and platform decisions. High enough to see the whole system, low enough to be blamed when it breaks.
Filed at 3,000 m
Event-driven or request-reply, chosen on purpose
A short decision guide for people tired of the debate.
Designing sharing models for many business units
One org, many owners, and the access model that has to keep everyone honest.
The architecture review board people actually attend
Fewer slides, faster answers, and decisions written down where people can find them.
Release trains for teams that hate trains
A shared cadence without the ceremony, for platforms with too many teams.