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 practical architecture pattern for isolating failed integration work, preserving appropriate recovery context, and enabling safe replay without turning transient failures into permanent data loss.
Read article →A production architecture guide to protecting event consumers and downstream systems when event arrival rates exceed processing capacity.
Read article →Event producers and consumers evolve independently. This deep dive explores additive change, semantic compatibility, versioning and migration without turning the event bus into a coordination bottleneck.
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 guide to reliable event publication and consumption when business state, brokers, databases, and external systems cannot share one atomic transaction.
Read article →A practical framework for choosing between retry, replay, dead-letter queues, and an Error Hospital based on failure semantics, recovery needs, and operational complexity.
Read article →Salesforce Change Data Capture consumers should treat ChangeEventHeader as processing metadata, not just jump directly to changed business fields.
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 →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 →