Salesforce ArchitectureArchitect (Hardest)data-meshdata-strategygovernance
Architect data mesh strategy with Salesforce as domain data product publisher
Real World Scenario
CIO mandates data mesh; CRM team asked how Salesforce participates as domain without becoming enterprise data swamp.
Expected Answer
• Salesforce owns customer engagement domain data product not all enterprise data
• Publish certified datasets via Data Cloud or API with SLA freshness schema owner
• Domain team accountable data quality scorecard not central IT alone
• Self-serve access via catalog with privacy classification
• Avoid mesh excuse for duplicate Account in 6 systems without ownership
• Federated governance council approves cross-domain joins
• Measure data product consumption not only pipeline count
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Salesforce owns customer engagement domain data product not all enterprise data. Publish certified datasets via Data Cloud or API with SLA freshness schema owner. Pick based on your integration pattern and team capability. Data mesh assigns ownership—Salesforce is one domain product among many not enterprise lake. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Data mesh assigns ownership—Salesforce is one domain product among many not enterprise lake.