Sizing volumes, latency and API allocations
Size an integration against its limits: daily API request arithmetic by edition and license, platform event publishing versus delivery allocations, event filters and parallel subscriptions, Bulk API 2.0 throughput levers, latency levers from gzip to Platform Cache and SOSL, callout timeouts, ownership skew and large file uploads.
Given a use case, identify performance needs (volumes, response times, latency) and propose appropriate integration solutions that will meet business requirements.
~8 min read · 16 practice questions ·
What the exam expects
- Calculate an org's daily API request allocation from its edition and licenses and compare it with an integration's estimate.
- Size platform event publishing and delivery, and shrink delivery with filtered custom channels or speed triggers with parallel subscriptions.
- Shorten bulk loads and extracts (operation choice, delta-only fields, parallel result downloads) and move next-day data to batch.
- Cut response time with gzip, Platform Cache, SOSL and selective indexed filters, within callout timeouts.
- Spot volume side effects: ownership skew from the integration user, file size limits, billions of rows.
Key terms: allocation (an org-wide budget, not per user); event delivery (events delivered to API subscribers such as Pub/Sub API clients); partition key (field whose hash picks a parallel subscription); selective filter (one the optimizer can drive from an index); ownership data skew (one user owns more than 10,000 records of an object).
Key facts
- Detail
- 100,000 + 1,000 per Salesforce or Platform license + add-ons
- Detail
- 100,000 + 5,000 per Salesforce or Platform license + add-ons
- Detail
- 50,000 Performance and Unlimited; 25,000 Enterprise
- Detail
- 250,000 Performance, Unlimited and Enterprise
- Detail
- Up to 10 partitions; custom high-volume events only
- Detail
- Up to five result URIs per call; API 58.0+
- Detail
- 10 s default; 120 s cumulative per transaction
- Detail
- Under 10% of records, up to 333,333
- Detail
- Up to 2 GB
Sources for this section (7)
- API Request Limitsdeveloper.salesforce.com (opens in a new tab)
- Platform Event Allocationsdeveloper.salesforce.com (opens in a new tab)
- Parallel Subscriptionsdeveloper.salesforce.com (opens in a new tab)
- Get Parallel Resultsdeveloper.salesforce.com (opens in a new tab)
- Callout Limitsdeveloper.salesforce.com (opens in a new tab)
- Indexesdeveloper.salesforce.com (opens in a new tab)
- Insert or Update Blob Datadeveloper.salesforce.com (opens in a new tab)
- Why doesn't adding integration users raise an org's API capacity?
- When does a filter reduce a subscriber's delivery usage?
- What is the default Apex callout timeout?
- Why should a high-volume integration user have no role?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 25 lessons of the Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (16 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams