The complete collection of Deep Dives, practical tutorials, Quick Reads and engineering notes across Salesforce, MuleSoft, DataWeave, integration, APIs, distributed systems, testing and developer tooling.
Looking specifically for longer-form architecture and production engineering? Explore the 12 curated Deep Dives →
A practical architecture and implementation guide for consuming Salesforce Change Data Capture events with MuleSoft while designing replay, idempotency, recovery, and downstream processing deliberately.
Read article →A practical guide to consuming Salesforce Platform Events with MuleSoft, with replay, checkpointing, idempotency, durable handoff, and recovery considerations.
Read article →A production architecture guide to protecting event consumers and downstream systems when event arrival rates exceed processing capacity.
Read article →A production design for consuming high-volume Salesforce Change Data Capture events without depending on the 72-hour event-bus window: durable handoff, replay checkpoints, sequencing, parallel processing, backpressure and recoverable error handling.
Read article →A practical architecture for consuming Salesforce CDC and Platform Events reliably, with replay checkpoints, idempotency, recovery paths, observability, and downstream failure handling.
Read article →A practical decision guide for choosing Salesforce Bulk API 2.0 instead of record-by-record REST calls when MuleSoft integrations handle larger datasets.
Read article →Salesforce Change Data Capture consumers should treat ChangeEventHeader as processing metadata, not just jump directly to changed business fields.
Read article →Understand what Salesforce Change Data Capture Replay IDs represent, how they support event recovery, and why they should be treated as opaque stream positions rather than business sequence numbers.
Read article →A concise architecture guide to choosing Salesforce Change Data Capture or Platform Events based on whether you need record-change notifications or purpose-built business events.
Read article →A practical guide to using Salesforce Composite API from MuleSoft when multiple related Salesforce REST operations belong in one request.
Read article →Salesforce record IDs identify Salesforce records; external IDs help systems agree on business identity. That difference matters for durable integrations.
Read article →Salesforce Pub/Sub API is pull-based. Use its event-request model as a real backpressure mechanism instead of building an ever-growing consumer backlog.
Read article →A practical guide to using Salesforce External IDs for idempotent create-or-update integrations from MuleSoft without depending on Salesforce record IDs.
Read article →