Salesforce Integration Architecture

Certified Integration Architecture Designer and Identity & Access Management Architect. I design how Salesforce talks to the rest of your estate — auth done properly, patterns chosen for their failure modes, and 15+ banking integrations delivered inside a regulated fintech.

When You Need This

  • Integrations were added one project at a time, and nobody can draw the full picture.
  • Credentials live in metadata as passwords, and security wants them gone.
  • You're moving to event-driven and need to know what belongs on Platform Events versus REST.
  • A regulator or client security review is asking questions your team can't answer.

What Gets Built

  • Integration inventory and an architecture map of the current state
  • Auth model design: OAuth 2.0, JWT bearer flows, external credentials and named principals — no long-lived secrets
  • Pattern selection by volume, latency, and failure semantics: REST/composite, Platform Events, Change Data Capture, Bulk API
  • Error handling, retry, and monitoring design for every interface
  • Target architecture and a migration roadmap your team can execute

Engagement

Integration Architecture Review

€2,000 – 3,500

A structured review of your integration landscape, ending in a target architecture and a roadmap. Design and build work continues at day rate.

  • Auth model audit — flows, credentials, rotation
  • Integration inventory + architecture map
  • Target architecture + migration roadmap
  • 1-hour debrief call
Get in Touch

Proof

At Ebury (UK fintech), I delivered integrations across the estate: 15+ banking integrations, and the sales-communications stack — Vonage telephony with a separate regional provider for reliable LATAM call quality, plus WhatsApp and LinkedIn — and ran a security audit spanning the 1,500-user org and its 50+ integrations.

Read the Ebury case study

Certified Integration Architecture Designer and Identity & Access Management Architect. The same secretless-auth discipline is public in my OIDC-based GitHub Actions modules — no long-lived keys anywhere.

Frequently Asked Questions

REST callouts or Platform Events — how do you choose?

By failure semantics, not fashion. Request-response where the caller needs the answer now: REST or composite API. Fire-and-forget fan-out where consumers can catch up: Platform Events or Change Data Capture. High-volume batch: Bulk API. I document the decision so the next engineer knows why.

Do we need MuleSoft or other middleware?

Middleware earns its place when you have many systems, orchestration, or transformation-heavy flows. Point-to-point is fine until it isn't. I've delivered both and will tell you honestly which side of that line you're on.

How should Salesforce integrations handle credentials?

OAuth 2.0 client credentials or JWT bearer flows through external credentials and named principals — no passwords in metadata, no long-lived secrets, and rotation that doesn't require a deployment.

Tell me about the integration nobody owns

Book a 30-minute call — you'll leave with an honest read on whether I can help and what it would cost. No pitch, no pressure.

Book a Discovery Call Email About Scope

What happens next

  1. 1. A 30-minute discovery call about your situation.
  2. 2. A scheduled start date — typically within 2–4 weeks.

Related: Salesforce CI/CD & release engineering · fractional technical leadership