When you send a request to an API and it gets processed the API might want to notify you app about the status of the request. In order for your application to handle this callback you would have to set up an endpoint to listen for the notification and then send the url of that endpoint to the API. For example Twilio, one of the most popular public APIs,
Validating data can be easy with Mule if your message payloads are in certain formats. XML payloads, for instance, can be verified for correctness via XML schema or XPath filters. Payload type filters and OGNL expression evaluation can go a long way in asserting your POJO payloads are correct. Payloads with less structure, like Map or JSON data, are a little bit trickier to validate. This is particularly true on the front-end of web-services where leniency in data format,
Before streaming APIs, if you wanted to know if there were any updates on a specific event you had to query the API periodically and check if updates indeed occurred. Most likely, many of these queries would probably return no results as no new event happened but still resources were consumed in the process including the API call and parsing the response. Now, what if you want to get notified not only of 1 event but 10,
We are pleased to announce the Beta Milestone 5 release of Mule Studio, the graphical design tool for Mule ESB. At its core, it is based on the Eclipse Development Platform which many developers are already familiar with. But we have added significant functionality to it to achieve a very tight integration to Mule ESB. This makes Mule Studio a powerful visual and coding environment for developing Mule ESB applications.
In this blog post I will show how to extend Mule in a simple way using the recently released Mule DevKit. The goal of the Mule DevKit is to accelerate the development of Mule extensions by abstracting you from Mule specific stuff so that you just focus on what your are trying to build.
My idea here is to create a simple Cloud Connector to interact with Google Maps API but the concepts covered here can be used in other scenarios as well.
This post is all about developing Cloud Connectors and deploying apps to Mule iON, but rather than just using words I created a screencast that demonstrates how to use Cloud connectors and Mule Flow to build applications that can be run on Mule or Mule iON.
We live in a world where the slow one is left behind. You company must adapt to the ever changing and complex world of technology integration. We live in a world where it is no longer acceptable to take months to integrate new services. So today’s post is about speed. I will show how you can build a Cloud Connector for Mule in five easy steps. The same cloud connector that you will be able to use on Mule standalone or Mule iON to integrate into your company.
Once you have a working Mule ESB application you may be wondering how fast it can run. Here we will discuss a simple method for measuring the throughput of your application using Apache JMeter.
Bear in mind there are many ways to improve performance (simple changes can yield great performance boosts). We will explore them in greater detail in a follow-up blog post covering Mule application tuning.
Last time that I blogged about Studio was when we had a limited private beta. The program went really well and we got a lot of great feedback. Now, I’m really happy to announce that we have released Mule Studio (beta) to the public. You can download it from here. Mule Studio is free and anyone can use it.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.