john.demic on Wednesday, November 30, 2011

Implementing Custom Validation with DevKit


Validating data can be easy with 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, particularly JSON, can be beneficial.  In these cases a custom Message Processor is usually necessary to filter or sanitise the data.

Application stacks are so passé, now its all about the slice. With the rise of open APIs we are seeing a new breed of . Infrastructure APIs are cropping up everywhere for doing things like , FTP, monitoring and management, analytics and application security.  These slices of functionality, delivered as services, remove the time consuming need to set up services locally and allow developers to spend their time building their application. Adoption of these infrastructure means application architecture doesn’t look the same as it did. Piece by piece the sub systems for an application such as data, security, user management, , integration and messaging are being hosted outside the application. Furthermore, there is a wealth of new services available to applications providing new capabilities such as telephony, facial recognition, address validation, geocoding/geolocation, social media mining, carbon footprint calculators – pretty much anything you need and more to build your killer app. This means application development is becoming a lot more about composition of of , not coding it all yourself.

Before 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, 20 or 100? Wasting resources like this is not acceptable both for a the consuming the API and for the API provider and that is why streaming emerged.

Kira on Wednesday, November 23, 2011

Get the most out of Mule HA clusters


3.2 introduced out-of-the-box clustering and reliability patterns. Want learn get the most out of these new capabilities?

Mike Schilling, MuleSoft’s Lead Architect, shares his in depth knowledge about Mule 3.2′s HA clusters.  If you are looking learn the leading tips and tricks for designing and managing clusters, as well as the applications running on the cluster, you should plan to attend MuleSoft’s upcoming webinar titled: High Availability for Integration Applications.

At QCon SF last week I gave my talk on DevOps to NoOps: 10 cloud services you should be using. I talked about what I call the API explosion and how that impacts the way we build applications before introducing my list. I focused on infrastructure APIs because I believe these have the biggest impact on development and thus the developers that build applications. For me, the interesting part of the talk was the questions, it highlighted the general reaction to the benefits of infrastructure – if you are not using them you probably don’t get the value.

Of all the professional networks available LinkedIn has clearly taken the lead with more than 120 million members. Do you use LinkedIn? Most likely you do! That’s why we thought it’s important to have a Connector to interact with LinkedIn and take advantage of its social power.

When developing a Mule Application the normal way to define an statement is by declaring it directly in the connector, as shown in the following snippet.

However is possible that you’ll face a situation in which you have to use large and complex queries. For that scenario the previous approach is not adequate since you’ll end up with a configuration difficult to read. So the best thing to do is to externalize these queries in one or more files.

around public cloud offerings has always been a major point of concern (and controversy) for users. How do cloud providers protect customer data? How is log data protected? How is the surrounding infrastructure secured? We previous talked about how iON stays up and running even through EC2 outages. Today, we will talk about iON security to show how we protect customer information and the infrastructure used in building iON.


We are pleased to announce the Beta Milestone 5 release of Mule Studio, the graphical design tool for 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 a powerful visual and coding environment for developing Mule ESB applications.

The last time we talked I show you how you can easily build RESTful APIs on top of iON.  I just covered just a very narrow scenario, the sky is the limit when talking about the kind of integrations that you can build using iON. So this week I’m going to walk you through another interesting use case, IVRs. If you don’t know what they are, don’t worry I will cover the basics in this article. Stick around it’s going to be wild.