Headless 360Architect (Hardest)composablearchitecturestrategy
Evaluate composable commerce vs monolithic Salesforce Commerce
Real World Scenario
CTO proposes replacing B2C Commerce with composable best-of-breed cart, PIM, and OMS while keeping Salesforce CRM.
Expected Answer
• Composable offers flexibility but integration tax and operational complexity
• Assess team maturity for multi-vendor ops vs Salesforce unified stack
• Salesforce CRM + Commerce integration benefits reduced with external cart
• Define clear system of record per domain: cart, inventory, pricing, orders
• MuleSoft or iPaaS becomes critical path for composable success
• TCO includes 24/7 on-call across vendors not single Salesforce support case
• Hybrid: composable PIM/search with Salesforce order management if fit aligns
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Composable offers flexibility but integration tax and operational complexity Also consider: Assess team maturity for multi-vendor ops vs Salesforce unified stack In practice: Salesforce CRM + Commerce integration benefits reduced with external cart Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Composable is organizational capability statement—architects quantify integration FTE before endorsing best-of-breed.