IntegrationArchitect (Hardest)multi-orgevent-hubenterprise
Handle Salesforce multi-org integration with event hub pattern
Real World Scenario
Global company has 8 regional Salesforce orgs; HQ needs consolidated customer view and cross-region case escalation.
Expected Answer
• Enterprise event hub (Kafka/MuleSoft) receiving CDC from each org with OrgId dimension
• Data Cloud or warehouse consolidating cross-org profiles with identity resolution
• Cross-org case referral via API or centralized service org pattern
• Avoid point-to-point 8x8 org connections—hub and spoke mandatory
• Metadata harmonization: aligned picklist values and external ID schemes
• Regional data residency may prohibit single global hub—federated hubs
• Governance council for cross-org integration standards
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Stay within limits by: Enterprise event hub (Kafka/MuleSoft) receiving CDC from each org with OrgId dimension. Bulkify everything — never query or DML in loops. Cross-org case referral via API or centralized service org pattern. Multi-org integration complexity grows quadratically—hub pattern is architectural necessity not preference. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Multi-org integration complexity grows quadratically—hub pattern is architectural necessity not preference.