In our upcoming MuleSoft webinar, “‘The Health Cloud’: Are we there yet?”, we’ll be talking all about healthcare and the cloud. There has been quite a bit of  talk about a “Health Cloud” which promises to extend the point of care, improve patient outcomes, enable closer clinical collaboration and lower costs, but have healthcare organizations really embraced the cloud? Or is this another case of media hype? With such confidential information at risk, how are organizations dealing with data security and integration with third party applications and ?

Priya Sony on Tuesday, November 5, 2013

API Management Best Practices eBook

2

With the launch of APIhub.com, acquisition of ProgrammableWeb and launch of the RAML spec we co-developed with Box, LinkedIn, Intuit and others – we are investing heavily in the API space to help developers take part in the API economy. APIs are unlocking massive business value and customers are turning to us more and more to help make their API vision a reality.

To take our love for APIs a step further, we’ve created a new easy to digest, “7 Habits of Highly Effective API and Service Management” eBook (complete with exciting graphics), we’d like to share with you!

reza.shafii on Monday, November 4, 2013

Introducing APIkit

2

Hot on the heels of the announcement of the RESTful API Modeling Language () by the RAML working group, I am very happy to announce the general availability of APIkit.

APIkit consists of a set of open source Maven and Mule Studio-based tools that enable developers to be massively productive in creating well-designed REST APIs.  APIkit features include the ability to take a REST API designed in RAML, automatically generate backend implementation flows for it, and then run and test the API with a pre-packaged console.

Get Ready to RAML

Uri on Monday, November 4, 2013

RAML Web Tooling Unleashed!

0

I’m excited to announce that we’ve recently made available to the RAML community a new API Designer, API Console, and API Notebook, built around a new JavaScript parser released as part of the workgroup. All of these are available under open-source licenses, and all may either be downloaded and used on your own site or are hosted as part of the APIhub.com service. You can find them on the projects page of RAML.org.

How did we get here?

Priya Sony on Monday, November 4, 2013

Monday blues?

0

Having trouble getting going this Monday? Daylight savings throwing off your routine? Check out this fun video to get your day started!

Release 34 is now live! With this release we’ve made a number of improvements to to make managing your integrations easier. These include the ability to promote applications from sandboxes, workers for problems, create secure environment variables, and scale applications vertically, as well as horizontally.

Here at MuleSoft, we’ve had a lot of exciting things going on lately. With our new lean startup mountain climbing principles, MuleSoft summits wrapping up and the launch of RAML tooling, we’ve been pretty busy; not to mention we’ve been hiring talent like crazy!

We thought it might be a good idea to give our community an idea of what goes on internally – what we’re up to, who we are, what makes us laugh – and just shed some light on MuleSoft and the personalities we have here.

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.

Today I’m going to share some valuables lessons learned about developing highly concurrent software. These are real life lessons that come straight from the development of the Mule ESB. This is a story about deadlocks, context switches, CPU usage and , focusing in how to diagnose this issues which is often the hardest part of the solution.

So the story begins a couple of weeks ago when I started working on a new feature for Mule 3.5.0. You’ll hear the details about it soon enough but basically it’s a new feature that aims to address integration use cases which requires processing huge amount of data. As you can imagine then, this feature has to deal with parallelization, process management, atomicity, consistency, distributed locks, etc…. All the fun stuff!

This post is brought to you by… you! Yes, a couple of weeks back I was writing about how dealing with OAuth2 secured APIs got way easier since Mule’s August 2013 Release. We got such a great feedback that we decided to incorporate some of it in our latest October 2013 release.

 

 

Token Management vs. Token Nightmare

So let’s do a quick recap. In the last post we said that now Mule is way smarter at automatically handling your tokens. So, in a single tenant scenario you could just do this: