// S-01
Integration frameworks
Inbound and outbound REST, built once and reused.
// what it is
An integration framework is one standard way for Salesforce to call external systems and to be called by them. Each new connection is built on the same framework, so no integration brings its own approach to callouts, errors and tests.
Where Salesforce is not the system of record, the framework can include a data-access layer for off-platform data, so the platform stays performant, secure and maintainable.
// when a team needs it
- Every integration in the org has been built differently and each is hard to maintain.
- Salesforce needs to read and write data it doesn't own.
- More integrations are on the roadmap and you want them built on one pattern.
// what you get
- An inbound and outbound REST integration framework in Apex, built once and reused.
- A data-access layer for off-platform data sources, where you need one.
- Documented designs your developers can follow for the next integration.
- Code review while the team adopts it.
// where I've done this
- Hargreaves LansdownDesigned and built the practice's inbound and outbound integration framework, standardising how Salesforce connects to external systems and services.
- Hargreaves LansdownArchitected the core CRUD data-access layer for off-platform data sources where Salesforce is not the system of record.
- CertiniaCo-created an off-platform resource-matching engine callable from Salesforce orgs, built with Python and AWS.
// contact
Available for contract work alongside a full-time role.
UK / Remote