Back in the old days when I used to write SaaS integration apps for living (long time ago, like 2 months back…) I always found it somehow difficult to reconcile large datasets with the Anypoint Cloud Connectors. Don’t get me wrong, I love those connectors! They solve a lot of issues for me, from actually dealing with the API to handle security and reconnection. However, there’re use cases in which you want to retrieve large amounts of data from a Cloud Connectors (let’s say retrieve my 600K Salesforce contacts and put them in a CSV file). You just can’t pass that amount of information in one single API call, not to even mention that you’ll most likely won’t even be able to hold all of those contacts in memory. All of these puts you in a situation in which you will need to get the information in pages.
Tag: Mule Studio
In the past, as now, Mule ESB follows a release schedule that introduces a new version of our industry-leading ESB software every 9 – 12 months, supplemented with maintenance releases approximately every 6 months. Though this cadence fit very tightly with the demands of our customers who deploy Mule on premises, we came to realize that our customers deploying Mule to CloudHub were much more flexible in terms of updating versions of software, and were more eager to take advantage of new features and functionality.
I’m no psychic but I bet you two things: This holiday you already took a bunch of pictures that went straight into facebook and you drank A LOT. Now you’ll probably edit your photos in the morning, but it seems a shame to lose those drunken shots. What if you could save them? Let’s see how you can do that using Mule. We’ll see how we can make an app that pulls all our facebook photos and upload them into box.
We got you something special for Christmas this year.
We didn’t have time to wrap it, but we know you’re going to love it. We’re so excited to see the look on your face when you [download and] unpack your shiny, new Eclipse-based IDE. That’s right, we got you a brand new Mule Studio!
‘Twas the day after Christmas and all through the house, not a creature was stirring, because they were all playing with video games, smart phones, e-gadgets, and iParaphenalia. If you’re already in the mindset of playing with a new toy, why not explore the world of Mule Studio? It’s free, it takes a just a few minutes to download, and you can whip through our Getting Started guide in the time it takes drink another round of eggnog.
We are making this release of Studio available to the Mule community to get valuable feedback on our latest and greatest features. This blog post contains text and video introductions to the freshly-baked features included in this release.
As you read through this post and try the Studio features, please keep in mind that this is a pre-Beta version. Explore, discover and play, but do not use it to develop Mule apps for use in production.
Integration is becoming such a critical part of application development that we spend many of our cycles on making Mule easier for any developer to use. Mule Studio was built to address the needs of developers who don’t wake up every morning thinking about integration.
If you have used Mule in the last year there is a good chance that you have used Mule Studio. It is an Eclipsed based development environment for building Mule applications either visually or using the XML DSL (with full two-way editing). Mule Studio has become the preferred on-ramp to working with Mule. Of course if you prefer to hack in a text editor Mule continues to embrace Maven for command-line development.
But there are a lot of use cases where this kind of cross domain HTTP request is desired, so developers came up with some workarounds:
- Server side proxy: the idea is to avoid cross domain requests in the browser by doing them on the server:To do that in Mule you can use the HTTP proxy pattern as explained in this post.
Have you ever tried to move already created elements through the canvas in Mule Studio? Well, if you did, you may have figured out that the elements weren’t moved at all. You would probably have seen a black box while you were dragging elements into the canvas and nothing else; the elements were not transported.
Drag and drop support is important because when users use a tool like Mule Studio, they intuitively try to move elements. Furthermore, it saves a lot of work, since you don’t have to delete components from the canvas and then add them again from the palette; you can just move the components without the need of removing them. It makes your job easier, from the creation of the element, to the configuration. (When you decide to remove an element, you probably have already configured it).
Its that time of year again when we take the Mule team on the road for Mule Summit. In previous Summits we’ve had guest speakers from Forbes, Intuit, Facebook, Sky and the National Lottery all talking candidly about their use of Mule. The next round of Mule Summit events will be visiting even more cities with even more speakers.
Sign up today to join the core Mule development team and successful Mule users at the premier integration event of the year! Meet the experts and kickstart your integration project at Mule Summit, where you’ll have the opportunity to influence product direction and get hands on with Mule ESB and Mule Studio in our interactive labs.