Become a member

04 · Middleware or point-to-point?

Two systems talking directly is simple right up until it is three systems, then five. Where the line actually sits.

Article 10m 1 min read Updated 24 Nov 2025
04 · Middleware or point-to-point?
Modules
Apex Triggers
  1. Module overview
  2. 01 · Order of execution, the map
  3. 02 · One trigger per object
  4. 03 · The handler pattern
  5. 04 · Bulkification: 200 records or bust
  6. 05 · Recursion control
Data Model Basics
  1. Module overview
  2. 01 · Standard objects vs custom objects
  3. 02 · Relationship types, decided with three questions
  4. 03 · Record types and when not to use them
  5. 04 · Schema Builder, the honest map
  6. 05 · Junction objects in practice
Integration Patterns
  1. Module overview
  2. 01 · Request-reply with named credentials
  3. 02 · Fire-and-forget with platform events
  4. 03 · Batch sync without tears
  5. 04 · Middleware or point-to-point?
  6. 05 · Watch: a callout built end to end

Two systems talking directly is simple right up until it is three systems, then five. Where the line actually sits.

Count the edges

Point-to-point between n systems tends toward n² connections, each with its own auth, retries and error handling. Middleware turns that into n connections to one hub.

But do not buy a bus for one route

One Salesforce org calling one API does not need an integration platform. Start point-to-point behind a named credential; move to middleware when the third system shows up.

Practice in your org

  • Open your Developer Edition org and follow along step by step
  • Change one thing at a time and note what happens
  • When something breaks, read the error before searching for it