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 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 , 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?

reza.shafii on Thursday, February 27, 2014

Uncover the Secrets of a Great API

0

APIs enable companies to tap into digital assets to create new revenue streams, extend their value proposition through partner-delivered capabilities, and dramatically improve agility and responsiveness to new business opportunities. But APIs are no magical elixir. “Build it and they will come” may work in the movies, but in the universe of APIs, it couldn’t be further from the truth.

The success of an API hinges on adoption by the developer community – 3rd party developers in the case of public APIs, your own developers in the case of internal APIs – and achieving adoption requires careful planning at the outset. If you’re looking to improve an existing API, launch a new API initiative or just drive more adoption of your APIs, take a look at MuleSoft’s latest – “Secrets of a Great API”.

This whitepaper provides a set of guidelines to help you deliver winning API programs. In it you’ll learn what developers want, how to design for great user experience, proven strategies for driving developer adoption, and how to make your API stand out from the crowd. Get started by downloading the whitepaper today »

When we announced the December 2013 release, an exciting new feature also saw daylight: The Batch Module. If you haven’t read the post describing the feature’s highlights, you should, but today I’d like to focus on how the <batch:commit>block interacts with Anypoint™ Connectors and more specifically, how you can leverage your own connectors to take advantage of the feature.

<batch:commit> overview

In a nutshell, you can use a Batch Commit block to collect a subset of records for bulk upsert to an external source or service. For example, rather than upserting each individual contact (i.e. record) to Google Contacts, you can configure a Batch Commit to collect, lets say 100 records, and then upsert all of them to Google Contacts in one chunk. Within a batch step – the only place you can apply it – you can use a Batch Commit to wrap an outbound message processor. See the example below:



As companies adopt more and more SaaS applications, there is a pressing need to connect these applications to each other, as well as to legacy applications. Companies who don’t create connectivity between SaaS applications end up with information silos. Front office applications, without information from the system of record, don’t provide value. Back office data, if not surfaced in a system of engagement, is irrelevant.

What if you could connect all your SaaS and on-premises applications with a single platform? You could achieve a single view of your customer, across every application that touches the customer lifecycle. You could streamline your quote to cash office, removing error-prone, manual processes and accelerating the revenue cycle. You could unlock your back office by bringing relevant records and information into systems like Salesforce to bring value to your sales teams.

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!


Infographic: The API Economy Explained

Software is eating the world; APIs are eating software. So what is the API economy and how can you capture its value? Check out this infographic to find out!

 

Five Great API Ecosystem Lessons from Evernote

Building an API ecosystem into a platform is essential for joining the API economy. Evernote learned 5 important lessons on their path to “platformification”.

 
 

Happy Friday!

This week’s Meet a Muley posts takes us over to the Digital Marketing team! As Sr Manager of Marketing and Analytics, Nima tackles MuleSoft’s analytics infrastructure as we scale. Read on to learn about why we consider him the star of all of MuleSoft’s dance-offs!

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

  • Who’s that good looking guy?

How did you find MuleSoft?

  • MuleSoft found me.

What were you doing before this?

  • Head of Internet Marketing @ eBay Advertising

How’d you end up deciding on MuleSoft?

  • It was an opportunity to work in a startup environment where I could take ownership, solve difficult problems, and be part of building something big. Working at MuleSoft gives me the opportunity to make an impact while doing what I love and there’s nothing more satisfying than that.