In the "Discovery" phase of integration architecture, the architect must translate abstract business needs into technical requirements. The most critical variables that define the Integration Pattern are Timing and Volume.
An architect cannot choose between the REST API, Streaming API, Bulk API, or Outbound Messaging without knowing:
* Latency Requirements: Does the business need the update in 200 milliseconds (Synchronous), 2 minutes (Near Real-Time), or 24 hours (Batch)?
* Frequency: Is the data updated every time a user clicks a button, or once at the end of the day?
* Volume: Are we moving 10 records at a time or 10 million?
Option A focuses on UI/UX and licensing, which are project management concerns. Option B focuses on resource allocation and governance. While important for the project, they do not inform the technical design of the data flow.
By specifically seeking out Timing aspects (Synchronous vs. Asynchronous) and Update Frequency, the architect can apply the Salesforce Integration Decision Matrix. For instance, a "Real-time" requirement for small volumes leads to a Request-Reply pattern via Apex Callouts. A "Nightly" requirement for large volumes leads to a Batch Data Synchronization pattern via the Bulk API. Identifying these "Non-Functional Requirements" (NFRs) early is the only way to ensure the architecture is scalable and stays within platform governor limits.

When dealing with multiple external service providers (like different regional shippers) that have varying API requirements, the most scalable architectural choice is an Enterprise Service Bus (ESB) or middleware solution. This scenario describes a classic "Orchestration" and "Transformation" use case.
An ESB excels at:
1. Routing/Mediation: The ESB can receive a single, standardized request from Salesforce ("Get Shipping Rates") and use business logic to determine which regional carrier's API should be called.
2. Transformation: Each carrier likely has a distinct XML or JSON schema. The ESB can transform the common data model sent by Salesforce into the specific format required by the chosen shipper.
3. Protocol Bridging: If one shipper uses SOAP and another uses REST, the ESB handles these technical differences, allowing Salesforce to interact with a single, simplified interface.
Option A (Apex REST) would require the Salesforce team to maintain custom code for every new shipping provider added, leading to high technical debt and maintenance challenges. Option C is incorrect because an ESB is a back-end infrastructure component, not a user interface tool.
By utilizing an ESB, Northern Trail Outfitters decouples Salesforce from the complexities of the shipping providers' APIs. This "Hub and Spoke" model means that adding a new regional shipper in the future only requires configuration within the ESB, rather than a full code deployment in Salesforce. This provides the agility and architectural separation necessary for a global retail operation.

When migrating from a legacy landscape to a modern platform like Salesforce, the most immediate technical hurdle is the diversity of system types and communication protocols used by the existing systems.
In a legacy environment, integrations are often not standardized. An architect may encounter systems that communicate via modern REST/SOAP APIs, but they will also likely find older systems that rely on Flat File exchanges (FTP/SFTP), Email-based triggers, or direct Database connections. These "System Types" are a fundamental constraint because they dictate the choice of integration middleware. For example, Salesforce cannot natively poll a file system or read an on-premise database; therefore, an architect must identify these constraints to justify the need for an ETL or ESB tool that can bridge these legacy protocols with Salesforce's API-centric architecture.
While reporting (Option B) and multi-currency (Option C) are important functional requirements for the Salesforce implementation, they do not dictate the integration pattern (e.g., Request-Reply vs. Batch) as much as the technical interface of the source/target systems does. By evaluating the APIs, file systems, and email capabilities of the legacy landscape first, the architect ensures that the chosen integration mechanism- whether it be the Streaming API, Bulk API, or middleware orchestration-is technically capable of actually communicating with the legacy debt.

When building custom mobile or web applications that aim to replicate the look and feel of Salesforce Lightning Experience, the User Interface (UI) API is the architecturally recommended choice.
The UI API is specifically designed to provide the metadata and data needed to build high-fidelity user interfaces. Unlike the standard REST API (Option B), which returns raw record data, the UI API returns both data and metadata in a single response. This includes information about page layouts, field-level security, picklist values, and localized labels. By using the UI API, the mobile app can dynamically render fields according to the user's permissions and the organization's layout configurations, ensuring that the custom app stays in sync with changes made in Salesforce Setup without requiring code updates in the mobile app.
Connect REST API (Option A) is primarily used for Chatter, Communities (Experience Cloud), and CMS content, and while it is useful for those specific social features, it does not provide the layout and record-level metadata required for a full CRM interface. The UI API is the same underlying technology that powers the Salesforce mobile app and Lightning Experience itself. Therefore, utilizing this API allows NTO's developers to build a native app that perfectly mimics the Lightning Experience while reducing the amount of custom logic needed to handle complex Salesforce UI requirements.

To satisfy a requirement for near real-time REST updates with limited development resources, the architect should utilize Flow Builder. Flow Builder is Salesforce's primary low-code tool for automating complex business logic and outbound integrations.
The Remote Process Invocation-Fire and Forget pattern is the most efficient way to signal an external system (or middleware) that a record was created without blocking the user. Using a Record-Triggered Flow on the Order object, the architect can configure an Action (such as an External Service or a simple HTTP Callout) to send the order data to the middleware's REST endpoint.
Option A is slightly incorrect because creating a platform event is just one step in an event-driven flow; the
"Fire and Forget" pattern more accurately describes the end-to-end intent. Option B (Change Data Capture) is a powerful tool, but it is considered a "pro-code" or high-configuration so12lution on the middleware side, requiring the middleware to manage Replay IDs and Bayeux subscriptions. Option C leverages the native strengths of Flow to fulfill the requirement declaratively, 13allowing the team to14 deliver a functional integration without writing Apex code while meeting the near-real-time performance expectations of the ERP.