MuleSoft Champions are the life-blood of the MuleSoft community – experts who work tirelessly to give back to the community – whether it be through core contributions, creating connectors, writing blog posts, or through answering questions on our forums and StackOverflow.

For the work that our Champions do, we cannot recognize them enough. First we started with the creation of the MuleSoft Champions Program of which only 7 people have reached the highest honor, becoming a MuleSoft Champion.

Read more

Are you a developer using or interested in using Mule ESB, Anypoint Studio, Anypoint Platform™, or RAML? If so, we’d like to invite you to come hang out and meet the MuleSoft team next Thursday, March 12 at 6pm, at the Cartoon Art Museum in beautiful San Francisco!

Registration is limited and required, so make sure to register soon! We’ll be kicking things off with plenty of food and drinks, a few surprise guests, and a chance to meet and chat with MuleSoft’s founder, Ross Mason.

Read more

This is part seven of the API design best practices series. Read part one of the series. 

Looking Back

Unfortunately, this series of API Best Practices has come to a close. Over the last several months we’ve taken a look at how to design a flexible, extensible, and usable API. These steps included:

Read more

This is part five of the API design best practices series.  

Read more

• Read part one: Plan Your API »
• Read part two: Spec Driven Development »
• Read part three: Nouns, CRUD, and more »
• Read part four: Hypermedia » 
• Read part five:Respond Handling »  

Welcome to the first episode of Meetups@MuleSoft, a new podcast series that highlights some of the coolest meetup groups in the San Francisco area. In this episode, we’re talking about ProtoNight – a meetup where ideas meet developers, FreeCodeCamp.com, Fiskkit, Xiki, and a recap of the 2014 APICon hackathon.

A special thank you to everyone that participated in this inaugural Meetups@MuleSoft podcast!  

Read more

This is part five of the API design best practices series.  

• Read part one: Plan Your API »
• Read part two: Spec Driven Development »
• Read part three: Nouns, CRUD, and more »
• Read part four: Hypermedia » 

Provide Helpful Responses

Building a solid foundation to ensure the scalability and longevity of your API is crucial, but just as crucial is ensuring that developers can understand your API, and trust it to respond with the appropriate header codes and error messages.

Read more

This is part four, sub-series 3, of the API design best practices series. Jump to sub-series 1 of the hypermedia sub-series.

• Read part one: Plan Your API »
• Read part two: Spec Driven Development »
• Read part three: Nouns, CRUD, and more »

A Road Trip

First off, let me apologize for the delay in this third part of the hypermedia sub-series. Christmas meant a warm trip back to Minnesota, a road trip through the Texas panhandle, and numerous snow storms in between — until finally I had the chance to cut through the mountainous desert of Southern California on my way back to beautiful San Francisco.

Now I understand some of you are probably wondering what any of that has to do with this post, other than it’s about 3 weeks after promised. One of the greatest challenges of the drive was battling my way through the snow and construction, and just hoping that the interstate would stay open (they literally close the interstates if it’s bad enough). But the one thing I could be sure of was that at every turn, between my steady GPS and road signs, I knew where I was going, and I knew when my path was being detoured or I couldn’t take a certain road… I knew this, because everything was nice and uniform.

Read more

This is part four, sub-series 2, of the API design best practices series. Jump to sub-series 1 of the hypermedia sub-series.

• Read part one: Plan Your API »
• Read part two: Spec Driven Development »
• Read part three: Nouns, CRUD, and more »

The Harsh Reality of the State of Hypermedia Specs

Hypermedia sounds great in theory, but theory only goes so far. Where hypermedia really shines, or completely fails, is in implementation. Unfortunately, as hypermedia is still a relatively new aspect of web based APIs, there isn’t one specified way of doing things. In fact, you’ll find that even some of the most popular APIs operate completely differently from each other.

Read more

This is part four, sub-series 1, of the API design best practices series.

• Read part one: Plan Your API »
• Read part two: Spec Driven Development »
• Read part three: Nouns, CRUD, and more »

What is Hypermedia

One of the challenges to implementing and correctly using hypermedia in your REST API is first understanding what hypermedia is, and what it means to use hypermedia as the engine of application state (HATEOAS).

Read more

This is part three of the API design best practices series.

• Read part one: Plan Your API »
• Read part two: Spec Driven Development »

Once you have an understanding of what your API needs to be able to do in order to meet your developer’s requirements, it’s important to ensure that it remains as flexible and extendable as possible.  Taking advantage of best practices not only means that your API will be familiar to developers, but also ensure that it remains fluid enough to extend and build on top of it in the future.  Here are this week’s best practices to help keep your API agile:

Read more