Data integration patterns

The communication between enterprise applications can be categorized as synchronous and asynchronous. Synchronous communication means that both client and server must be available at

In my last blog, I introduced terminology that can be used to label common concepts and patterns in the realm of digital integration. My

Integrating software is almost as old as writing software. From ETL to EAI to SOA, the software engineering industry has continually sought new integration

When I was interviewed for my role at MuleSoft a few months ago, I was asked if it was possible to have more than

This blog post is based on the internal work of Thomas Baumgart, former MuleSoft Client Architect, and is now being published by MuleSoft.   In previous

When surfacing data from systems of record, one of the concerns designers and developers need to address is the potential of retrieving an enormous

In the world of data integration, error handling is crucial to a successful data integration strategy, however, it is often one of the most

Asynchronous messaging enables applications to decouple from one another to improve performance, scalability, and reliability. This post will review the most common messaging patterns,

The Content Enricher is a useful content transformation pattern that elaborates a basic message with information from another system. A typical use case is

To streamline the integration process, MuleSoft has developed Anypoint Templates for Salesforce, packaging recurrent patterns to help developers work faster. (more…)