IntegrationArchitect (Hardest)event-drivenorder-fulfillmentmulesoft
Design event-driven order fulfillment with Platform Events and MuleSoft
Real World Scenario
Order placed in Commerce Cloud must trigger inventory check SAP allocation shipment label without synchronous 45-second chain.
Expected Answer
• Order_Placed__e Platform Event published on order confirm
• MuleSoft subscriber orchestrates inventory SAP shipping async
• Order status custom object Pending Allocated Shipped Failed
• Customer notified each status change via separate notification event
• Compensating cancel inventory if shipping label fails
• End-to-end correlation orderId across all events
• SLA monitor time from order to ship alert breaches
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Order_Placed__e Platform Event published on order confirm. MuleSoft subscriber orchestrates inventory SAP shipping async. Pick based on your integration pattern and team capability. Order fulfillment is canonical event-driven workflow—never chain 45 seconds synchronously. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Order fulfillment is canonical event-driven workflow—never chain 45 seconds synchronously.