# Inventorying interfaces with the integration pattern catalog

*Integration Architect Study Guide · Translate Needs to Integration Requirements · Last updated October 16, 2026 · https://www.certifyforce.com/study-guide/integration-architect/translate-needs-to-integration-requirements/inventorying-interfaces-with-the-integration-pattern-catalog*

How to turn a landscape diagram into an integration inventory: classify each interface against the six Salesforce integration patterns by direction, timing and storage, record its type, layer and key-tracking approach, and flag legacy mechanisms for modernization.

- Certification: Salesforce Integration Architect
- Exam section: Translate Needs to Integration Requirements
- Study guide: https://www.certifyforce.com/study-guide/integration-architect

**Official exam objective:**

> Given an existing system landscape diagram, create an inventory of the systems and integration patterns.

## What the exam expects

- Read a system landscape diagram and list each connection as an interface with its direction, timing and volume.
- Classify every data or process interface against the six patterns in Salesforce's integration pattern catalog, including flows that combine two patterns; UI mashups fall outside the catalog's scope.
- Record the integration type (data, process, virtual), the coordination style (orchestration or choreography) and the architectural layer (UI, business process, data).
- Specify how each interface tracks state between systems through stored keys.
- Flag legacy mechanisms (CometD Streaming API and PushTopic, workflow outbound messages, Salesforce to Salesforce, scripted Data Loader jobs) and name their replacements.

Key terms: **interface** (one connection on the diagram); **integration pattern** (a design approach for an archetype scenario, not an implementation); **orchestration** (one central controller directs each step); **choreography** (participants act autonomously); **surrogate key** (the other system's unique identifier, stored for later updates).

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Patterns in the architect catalog | Six: Request and Reply, Fire and Forget, Batch Data Synchronization, Remote Call-In, UI Update Based on Data Changes, Data Virtualization | [Integration Patterns Overview](https://architect.salesforce.com/docs/architect/fundamentals/guide/integration-patterns.html) |
| Calls into Salesforce | Always synchronous request-reply; the caller may discard the response | [Integration Patterns Overview](https://architect.salesforce.com/docs/architect/fundamentals/guide/integration-patterns.html) |
| Batch Data Synchronization best fit (remote master) | Third-party ETL tool with change data capture calling Bulk API; control tables track last run | [Integration Patterns Overview](https://architect.salesforce.com/docs/architect/fundamentals/guide/integration-patterns.html) |
| Data Virtualization best fit | Salesforce Connect external objects, no copy in Salesforce | [Integration Patterns Overview](https://architect.salesforce.com/docs/architect/fundamentals/guide/integration-patterns.html) |
| UI Update recommended solution | Platform events consumed by a Lightning component; delivery and order not guaranteed | [Integration Patterns Overview](https://architect.salesforce.com/docs/architect/fundamentals/guide/integration-patterns.html) |
| Canvas, mashups, Lightning Out | User interface layer | [Layered Approach](https://trailhead.salesforce.com/content/learn/modules/app-integration-patterns/app-integration-patterns-2) |
| Salesforce to Salesforce | End of life; retiring Spring '27 | [Data Integration with Salesforce](https://architect.salesforce.com/docs/architect/decision-guides/guide/data-integration.html), [Integration Patterns Overview](https://architect.salesforce.com/docs/architect/fundamentals/guide/integration-patterns.html) |
| Cross-org adapter | View, and edit with CRUD enabled, records in another org without replication | [Data Integration with Salesforce](https://architect.salesforce.com/docs/architect/decision-guides/guide/data-integration.html) |

## Check yourself

- Why is an Apex REST service that the caller treats as "fire and forget" still classified as Remote Call-In?
- When does Salesforce store the remote system's key in an External ID field?
- When is a middleware-run multi-step process orchestration rather than choreography?

## Sources

- [Integration Patterns Overview](https://architect.salesforce.com/docs/architect/fundamentals/guide/integration-patterns.html)
- [Learn About Integration Patterns and Designs](https://trailhead.salesforce.com/content/learn/modules/app-integration-patterns/app-integration-patterns-1)
- [Improve Application Integration with Layered Approach](https://trailhead.salesforce.com/content/learn/modules/app-integration-patterns/app-integration-patterns-2)
- [Data Integration with Salesforce](https://architect.salesforce.com/docs/architect/decision-guides/guide/data-integration.html)
- [System Landscape](https://architect.salesforce.com/docs/architect/reference-diagrams/guide/section-system-landscape.html)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 16 linked practice questions, and unlimited timed mock exams are included with the Integration Architect pack (USD $19): https://www.certifyforce.com/practice-exams