Salesforce ArchitectureArchitect (Hardest)api-gatewaysecuritypartners
Design enterprise API gateway fronting Salesforce for partner ecosystem control
Real World Scenario
200 partners hit Salesforce REST directly; security wants rate limit WAF analytics and API key lifecycle at gateway.
Expected Answer
• API gateway MuleSoft Flex AWS API Gateway in front Salesforce
• Partners never receive Salesforce credentials OAuth via gateway broker
• Rate limit tier per partner contract SLA
• WAF OWASP rules bot protection
• Central analytics latency error rate per partner
• Developer portal gateway not Salesforce native only
• Breaking change gateway version shield partners from Salesforce API churn
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. API gateway MuleSoft Flex AWS API Gateway in front Salesforce. Partners never receive Salesforce credentials OAuth via gateway broker. Pick based on your integration pattern and team capability. Direct partner Salesforce access does not scale to 200—gateway is enterprise partner pattern. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Direct partner Salesforce access does not scale to 200—gateway is enterprise partner pattern.