Salesforce Event and Change-Delivery Decision

Overview

Choose the supported delivery contract from business semantics, entitlement, transport, ordering, replay, schema, security, and recovery evidence.

Prerequisites

• Business event or record-change definition, producer, consumers, latency, ordering, volume, and recovery objective
• Current org edition, event entitlements, permissions, channels, schema, delivery allocation, and support contract
• Consumer idempotency, checkpoint or replay state, dead-letter path, reconciliation, and backfill owner

Tool Discipline

Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts.

Current Contract

Pub/Sub API uses gRPC over HTTP/2 and Avro for platform events, Change Data Capture, and real-time event monitoring. CDC publishes near-real-time record changes and can emit gap or overflow events; other Salesforce delivery mechanisms have different contracts.