Salesforce High-Volume and Composite Operation

Overview

Choose an API from workload evidence, make every batch restartable, and prove final state across partial, asynchronous, and dependent outcomes.

Prerequisites

• Dataset classification, object dependencies, operation, expected counts, external IDs, and owners
• Current Bulk API 2.0, Composite, Graph, and sObject Collections documentation
• Org limits, automation cost, error budget, maintenance window, quarantine, and rollback plans

Tool Discipline

Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts.

Current Contract

Bulk API 2.0 performs asynchronous CSV ingest and large queries. Composite APIs combine supported REST subrequests with documented dependency and limit semantics; the best choice depends on volume, dependency graph, latency, and atomicity needs.