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 15 curated Deep Dives →
Practical DataWeave patterns for Salesforce integrations: contract mapping, null handling, field normalization, reusable functions, and keeping transformations maintainable.
Read article →Design SOQL for Salesforce large data volumes using selectivity, indexes, Query Plan analysis, stable pagination, Bulk API extraction patterns, and architecture-aware tradeoffs.
Read article →An architecture deep dive into production-grade MuleSoft–Salesforce integrations: API selection, synchronous and bulk patterns, CDC/Pub/Sub, idempotency, replay, resilience, security, observability, and recovery.
Read article →An architecture deep dive into reducing CDC noise, carrying correlation context, consuming with Pub/Sub API, and designing replay, idempotency, backpressure, and recovery.
Read article →A practical MuleSoft guide to choosing bulk-oriented Salesforce operations, designing asynchronous jobs, handling result sets, and avoiding memory-heavy large-volume flows.
Read article →A focused migration checklist for MuleSoft Salesforce Connector 12.x covering runtime and Java requirements, removed authentication, listener changes inherited from 11.x, and regression testing.
Read article →A practical guide to Salesforce Connector authentication in Mule 4, including OAuth Client Credentials, JWT, OAuth 2.0, SAML, migration considerations, and production design choices.
Read article →A production-oriented error-handling strategy for Salesforce integrations in MuleSoft, separating transient connectivity failures from validation, authorization, and business errors.
Read article →A practical observability model for MuleSoft Salesforce integrations covering correlation IDs, latency, Salesforce errors, event lag, replay checkpoints, bulk jobs, and actionable alerts.
Read article →How MuleSoft Salesforce Pub/Sub Connector consumes CDC and Platform Events, how replay options work, and what production consumers must add for durable processing.
Read article →Practical Salesforce Connector query patterns for MuleSoft: field selection, pagination, transformation boundaries, selectivity, and choosing a different API for large extracts.
Read article →Designing replay-safe MuleSoft Salesforce event consumers with durable replay checkpoints, Object Store, idempotency, and failure-window analysis.
Read article →How to use Salesforce Connector upsert and external IDs to build retry-safe MuleSoft integrations without creating duplicate Salesforce records.
Read article →Use Salesforce Change Data Capture enriched fields to carry stable identifiers and context on custom channels without querying the source record after every event.
Read article →A practical review of Salesforce CDC field enrichment, including the 10-field limit, payload semantics, and when a follow-up query is still appropriate.
Read article →Compare carrying stable context in Salesforce CDC enriched fields with issuing a Salesforce query after each change event.
Read article →A practical design guide to configuring enriched fields on Salesforce Change Data Capture custom-channel members.
Read article →Understand the metadata behind a Salesforce filtered Change Data Capture channel and how PlatformEventChannel and PlatformEventChannelMember fit together.
Read article →Design safer Salesforce custom-channel filter expressions by understanding their SOQL-like model, operation filtering, field filtering, and practical limits.
Read article →Combine Salesforce CDC filtering and field enrichment to build a smaller, more self-contained event stream for downstream integrations.
Read article →Use Salesforce custom channels and server-side event filters to deliver only the Platform Events or Change Data Capture events an integration actually needs.
Read article →A balanced architecture review of Salesforce event filtered channels: where they help, where they add coupling, and what they do not solve.
Read article →Compare Salesforce server-side custom-channel filtering with receiving a broad event stream and filtering it inside the integration client.
Read article →Connect Salesforce CDC custom channels to a production Pub/Sub API subscriber with correct Avro decoding, replay, flow control, and recovery thinking.
Read article →A practical guide to Salesforce SOQL aggregate functions and when to summarize data in the query instead of application code.
Read article →Practical SOQL patterns for TODAY, THIS_WEEK, LAST_N_DAYS, absolute DateTime ranges, and integration-friendly incremental queries.
Read article →Filter on Salesforce formula fields today, and understand the new Summer '26 FORMULA() in SOQL WHERE pilot before using calculated expressions directly in a query.
Read article →Understand the difference between WHERE and HAVING in SOQL and use HAVING to filter grouped Salesforce results.
Read article →Practical SOQL GROUP BY examples using COUNT, SUM, AVG, MIN, MAX, multiple fields, and date grouping.
Read article →Use IN and NOT IN for value sets, then use SOQL semi-joins and anti-joins to filter records based on related-object criteria.
Read article →Use SOQL LIKE correctly with percent and underscore wildcards, literal special characters, apostrophes, bind variables, and injection-safe dynamic queries.
Read article →Use NULL conditions correctly in SOQL and avoid confusing missing values with empty strings or business defaults.
Read article →Use ORDER BY and LIMIT deterministically, understand OFFSET's role, and choose safer pagination patterns for integrations and large Salesforce result sets.
Read article →Practical SOQL performance guidance for selective filters, indexed fields, leading wildcards, relationship queries, and incremental integrations.
Read article →Learn the two core SOQL relationship-query directions with practical Account, Contact, Opportunity, and custom-object examples.
Read article →Learn how to select all, standard, or custom fields in SOQL, when FIELDS() is convenient, and when an explicit field list is still the better production choice.
Read article →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 →