IntegrationAdvancedmulesoftscatter-gatherperformance
Design MuleSoft scatter-gather for parallel Salesforce API aggregation
Real World Scenario
Customer 360 API needs Account Contacts Cases Opportunities; sequential MuleSoft calls exceed 8 second Experience Cloud timeout.
Expected Answer
• Scatter-gather parallel Salesforce REST calls merge response
• Timeout scatter branch max branch not sum of calls
• Partial response return available data flag incomplete sections
• Cache Account header 60 seconds reduce repeat scatter
• GraphQL or Composite alternative single round trip evaluate
• Monitor scatter branch p95 identify slow object
• Circuit breaker per branch Account fail does not block Contact
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Scatter-gather parallel Salesforce REST calls merge response. Timeout scatter branch max branch not sum of calls. Pick based on your integration pattern and team capability. Scatter-gather beats sequential for read aggregation—set branch timeout not cumulative. Optimize for scale and operational observability.
Architect Perspective
Scatter-gather beats sequential for read aggregation—set branch timeout not cumulative.