Integration has been an enterprise challenge for a long time. In order to create the new products, applications, and services that businesses need to confront the digital revolution, you have to connect systems, data, and devices. There’s no way around it. Enterprises struggled with point-to-point integrations, which created a spaghetti-like mess of code, and then, […]
Picking up from the second part of this series, this blog post will wrap up building an end-to-end API solution. For the first post, you abstracted source systems with APIs to add flexibility, ease of consumption, and increase adoption and integration possibilities.
With as many systems of record available in the cloud– from SaaS applications like Salesforce to Netsuite – the need for a cloud-based enterprise messaging solution has now become necessary to support high availability, scalability, and reliability patterns in an Integration Platform as a Service (iPaaS) solution, such as MuleSoft’s CloudHub.
This post was written by one of the stars in our developer community, Rakesh Kumar Jha. As a MuleSoft Certified Architect, Designer and Developer, I recently worked on API implementations for one of our clients using MuleSoft’s CloudHub. One common feature that we used across our APIs implementations is reading a properties file in Mule flows.
Before we get started with this blog, if you haven’t checked out Part 1 of this Dev Guide series, make sure you work through that first, where we went through developing a resilient, governable, and flexible API layer on top of your source systems—what we call system APIs.
At MuleSoft, we are fortunate to have a community of developers that answer questions about Mule, share best practices, and organize meetups. Their knowledge and effort make building solutions with MuleSoft simpler and more rewarding.
Here at MuleSoft, we talk a lot about how API-led connectivity can speed up your development cycles, and I’m here to guide you through how to do it. The API-led approach is a natural evolution from developing libraries, writing digestible markdown files, and sharing them on GitHub.
Anypoint Platform offers a wide variety of Anypoint Connectors to facilitate easy integration with third-party applications. But what kinds of connectors are available in Anypoint Exchange and what are the most downloaded connectors for 2017?
MuleSoft’s DataWeave, which is now the main expression language in Mule 4 beta, is a powerful technology that can efficiently transform complex structured data between popular data formats, including JSON, XML, CSV, and Java objects. I’m a courseware developer and trainer at MuleSoft, and I’ve been spending a lot of time learning about DataWeave recently. Update, April 2018 […]
Over the past few months, I have been working with our Product and Engineering team on Crowd, the latest release of Anypoint Platform. The Crowd release consists of updates to Anypoint Exchange as well as the new Anypoint Designer Center in Anypoint Platform.