Salesforce ArchitectureArchitect (Hardest)operating-modelteamsintegration
Design shared services integration team operating model
Real World Scenario
Each project builds own MuleSoft flows duplicating SAP connectivity patterns.
Expected Answer
• Shared integration team owns reusable APIs and connectors
• Project teams consume not rebuild SAP API
• API product owner backlog for platform APIs
• SLA for new integration requests
• Chargeback or internal funding model
• Knowledge base runbooks for each certified integration
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Shared integration team owns reusable APIs and connectors. Project teams consume not rebuild SAP API. Pick based on your integration pattern and team capability. Reuse requires funded platform team—voluntary sharing fails at enterprise scale. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Reuse requires funded platform team—voluntary sharing fails at enterprise scale.