Integrating software is almost as old as writing software. From ETL to EAI to SOA, the software engineering industry has continually sought new integration methods to get quick access to data and functionality, avoid duplication of effort, and deal with federated ownership of applications. In the current cloud-native, highly-distributed software landscape, even the simplest mobile app is built on a complex, integrated back end. Web APIs have become ubiquitous in this landscape,
Read more
When I was interviewed for my role at MuleSoft a few months ago, I was asked if it was possible to have more than one System API layer. I froze — and it’s possible this question has crossed your mind as well.
After the interview, I sketched out some use cases to figure out the answer to this question. It did not take long for me to understand that API-led connectivity is not strictly restricted to three layers — System API,
Read more
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 blog posts, we’ve discussed business agility, the various types of architectures, and an API-led approach with Anypoint Platform. In this blog post, we’ll cover the differences between MuleSoft’s unique API-led approach and an SOA-based architecture.
Read more
When surfacing data from systems of record, one of the concerns designers and developers need to address is the potential of retrieving an enormous number of results in a single load session. This requires significant processing power on both the client and server sides and network traffic, and can degrade the overall data consumption and experience.
There are different approaches to address this concern, but one of the most widely used is the concept of pagination.
Read more
In the world of data integration, error handling is crucial to a successful data integration strategy, however, it is often one of the most overlooked areas because, quite frankly, it can be quite intimidating when you initially try and understand it. In my series of blog posts, I hope to reduce this complexity by breaking it up into simple concepts that are easier to digest.
Read more
Asynchronous messaging enables applications to decouple from one another to improve performance, scalability, and reliability. This post will review the most common messaging patterns, along with why and when to use them.
Read more
The Content Enricher is a useful content transformation pattern that elaborates a basic message with information from another system. A typical use case is described in the seminal work on integration patterns: Enterprise Integration Patterns, Gregor Hohpe and Bobby Woolf. Addison-Wesley Professional; October 20, 2003. It describes a scenario where one system may provide a customer ID, but the target system requires the customer name and address. This additional information must be retrieved from another system and combined with the customer ID to form the information required by the target system.
Read more
To streamline the integration process, MuleSoft has developed Anypoint Templates for Salesforce, packaging recurrent patterns to help developers work faster.
Read more
With the advent of next generation, easy to use integration toolsets, the following is becoming a very familiar scenario.
The business has a use case to move customer records from a database (DB) to Salesforce (SFDC). A system analyst in the line of business quickly creates an integration with a connector and deploys it.
A few weeks later, the customer support team comes up with another use case to display customer data on the support web portal.
Read more
Anypoint Templates showcase best practices around most common data integration patterns between two systems, for example, Salesforce and Workday, Salesforce and MS Dynamics CRM, Salesforce and NetSuite, Workday and ServiceNow and so on. With our new series of Pub/Sub templates, implemented using a publish/subscribe architecture, we are providing a more modularized approach to integration by allowing you to decouple source and destination systems and easily incorporate multiple systems without having to modify the existing integration application.
Read more
