IntegrationArchitect (Hardest)platform-eventscdcevent-driven
Architect event-driven integration with Platform Events and CDC
Real World Scenario
Nightly batch exports of Account changes cannot keep warehouse analytics current for same-day personalization.
Expected Answer
• Enable Change Data Capture on Account with field-level selection minimizing noise
• High-volume Platform Events for custom business signals CDC does not cover
• Middleware subscribers with replay ID recovery and idempotent processing
• Event schema registry with backward compatible versioning
• Separate read models in warehouse fed by event stream not batch ETL
• Monitor publish/subscribe lag and dead letter queues
• Complement with periodic reconciliation batch catching missed events
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Enable Change Data Capture on Account with field-level selection minimizing noise. High-volume Platform Events for custom business signals CDC does not cover. Pick based on your integration pattern and team capability. Event-driven is at-least-once—architect idempotent consumers and reconciliation from day one. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Event-driven is at-least-once—architect idempotent consumers and reconciliation from day one.