IntegrationArchitect (Hardest)cdcpulsarstreaming
Design Salesforce CDC to Apache Pulsar enterprise streaming pipeline
Real World Scenario
Enterprise messaging standard is Pulsar not Kafka; data platform requires Account CDC in multi-tenant Pulsar namespace.
Expected Answer
• Pub/Sub API gRPC consumer bridges Salesforce to Pulsar producer
• Pulsar topic per entity Account Contact with schema registry
• Geo-replicated Pulsar for DR alignment Hyperforce region
• Replay from stored ReplayId into Pulsar retention
• Compare Salesforce Event Relay AWS vs Pulsar bridge TCO
• Monitor lag Salesforce publish to Pulsar consume
• Idempotent Pulsar consumer dedup keys
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Pub/Sub API gRPC consumer bridges Salesforce to Pulsar producer. Pulsar topic per entity Account Contact with schema registry. Pick based on your integration pattern and team capability. Salesforce does not publish to Pulsar natively—Pub/Sub bridge is enterprise pattern. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Salesforce does not publish to Pulsar natively—Pub/Sub bridge is enterprise pattern.