Happy Friday!

For this week’s featured Muley, we thought we’d head over to the Channel and Services Team and introduce you to Samrah Khan, Director of Strategic Channel Partners! When she’s not in the office, she’s probably out doing yoga or checking out the newest restaurants. Read on to learn about her greatest weakness, what sets her apart, and why she’s one of our favorite Muleys!

First thought that came to mind when you looked into the mirror today?

  • OMG you need to get some more sleep – I’m getting old.

How did you find MuleSoft?

  • MuleSoft found me! I went through an extensive round of interviews and was very impressed by the rigorous process. Greg was inspiring and the culture was a good fit.

How did you first get interested in your field? 

  • In college I majored in Computer Science and joined a semiconductor company. Pretty soon I realized that I was bored out of my mind and I needed to do something different. I’ve always been a people person but I also love technology. Alliances seemed to be a natural fit.

All Demo, No Slides

Mule Studio makes it easy for developers to build hybrid integration applications. In our latest webinar, I’ll walk you through a demo on how to build a complete integration scenario and deploy it on a local machine on-premises, as well as to CloudHub. And what’s the point of building a hybrid integration application if you can’t manage it? I’ll then demonstrate the runtime management and monitoring capabilities available on the Anypoint Platform.

SaaS and APIs have changed the IT landscape. Applications you need to connect to now and in the future will be in a variety of languages and likely not in your datacenter. Limiting your next generation integration server by code base or deployment architecture will handcuff IT innovation, limiting your company’s ability to embrace future opportunity. .NET developers looking to get their company connected should think through these five questions before starting on their journey to a modern, loosely-coupled architecture.

How do I expose services in the style preferred by each client?

API ProtocolsThere are two major schools of thought for web services: SOAP/WSDL and REST. Given the large number of legacy systems in place in a typical enterprise, your integration software should meet the demands of each approach regardless of what is used by a given service. A modern integration engine can perform the heavy lifting to translate each message from the surfaced API into the form used by the target service. It can then transform and route messages while bridging different protocols along the way (e.g. HTTP to MSMQ). Using this method, clients become less dependent on interface and protocol requirements and service owners can vary services over time to meet changing business requirements while mitigating down time.

I’m excited to announce our early access release of Mule 3.5. We’ve continued to focus on making Mule simpler than ever and this release packs a huge punch in that department.  We’ve done a ground-up rethink of our database and web services connectivity, resulting in new connectors which help you integrate in fewer clicks than ever that are fully integrated with DataSense.  Also in this release are the new Shared Resources capabilities, allowing you to easily share connectors or other resources across loosely coupled applications in the same Mule container. Finally, this release contains many usability improvements, such as the ability to see the payload and message contents at design time, support for properties and variables with DataSense, batch improvements, and more.

Here’s our weekly roundup of the top 5 integration and API articles of the week.  Take a look, let us know if we missed any, and share your thoughts in the comments.  Don’t forget to follow @MuleSoft to stay up-to-date on integration & APIs!

APIs Are Bridging the Mobile App Gap

Mobile is the beginning of an entire new generation of businesses built around the customer, and the fuel of the next generation is the API.


The Internet Of Things: The Real Money Is The Internet, Not The Things

The Internet of Things is exploding, but the real opportunity is building pan-device business services.

This week’s Muley comes to us from the cloud integrations team in Buenos Aires! As an Engineering Manager, Alejandro focuses on keeping things running smoothly. Read on to learn about some of biggest challenges he has to overcome.

First thought that came to mind when you looked into the mirror today?

  • How hot I am, wait, I mean old… that was the word.

How did you find MuleSoft?

  • Nahuel Lofeudo, a fellow Muley, worked on my team at Travelocity and quit to come to MuleSoft. As a result, I hated MuleSoft! Little did I know I’d be here too.

The “Man-in-the-Middle” attack is such a well-recognized security risk, with established solutions and preventative measures in place that when I first heard about the recent ruckus around the Apple security flaw, I thought Apple’s trouble was more legal in natural, maybe some sort of royalties dispute between iTunes and the Michael Jackson estate. Only later did I found out what all the fuss was about “in the middle”, not “in the mirror”, and why I had to upgrade the iOS on my iPhone on a beautiful Saturday afternoon.

Regarding the specifics to Apple’s security flaw, there is already plenty of press coverage out there.  For example, David Auerbach wrote a great analysis over at Slate.com.

In this post, I’d like to illustrate how automated unit testing with appropriate code coverage could have detected that particular kind of error, the one caused by grammatically correct code that inadvertently invalidated the whole logic of the program. We will build the unit tests using the MUnit module, an open source Mule testing framework that significantly streamline and simplify the process of writing unit tests.

error handlingIf you look at the W3C document listing HTTP status codes, you may notice that only a small portion of all possible codes represents the happy path – i.e. 2xx codes. Most other codes are there to let client know that something went wrong with the request and the expected response cannot be returned. When building an APIKit-based application, developers must properly handle error conditions and set status codes accordingly. As always with Mule, there are many ways to achieve that. Let’s look at some of them.

Our use case is a very simple ACME Company API which returns a product information based on a particular product ID. In other words,

Here’s our weekly roundup of the top 5 integration and API articles of the week.  Take a look, let us know if we missed any, and share your thoughts in the comments.  Don’t forget to follow @MuleSoft to stay up-to-date on integration & APIs!

How GM Got Religion And Released An API

GM is betting big that software developers will help them take cars into the 21st century. The road to the future is built on APIs.


How Data Integration Is Changing the Enterprise Landscape

Complex integration challenges are changing the enterprise. Chief Data Officers will emerge to make sense of all the data integration needs.


Happy Friday Everyone!

This week’s featured Muley comes from our Documentation team! Robin Pille is the Technical Writer that helps make our Mule Documentation awesome. When she’s not immersed in a book or munching on a baguette, she’s probably out dancing the lindy hop.

First thought that came to mind when you looked into the mirror today?

  • I wish I had time to iron this blazer.

How did you find MuleSoft?

  • MuleSoft found me.

How did you first get interested in your field?