Announcing MuleSoft’s solutions for Microsoft!

Today, we announced the launch of MuleSoft’s Solutions for Microsoft. These new solutions enable companies to leverage existing Microsoft IT investments and integration logic written in .NET on Anypoint Platform™. Using our new .NET Connector and MSMQ Connector, developers no longer have to to be siloed by coding language or development framework. With MuleSoft’s solutions for Microsoft, developers can customize Mule application logic using any .NET language and familiar .NET development tools, including Visual Studio.

Trust no one! Most security issues comes from assuming that no bad person is going to tamper with your input data. We usually pay more attention to it when processing the most common inputs, such as an HTTP request or some argument that’s going into an SQL query. But we usually don’t pay much attention to other types of resources that are also vulnerable to malicious thinking – such as an file.

are an XML feature which allow you to embedded an external source into your document. For example, let’s suppose that your application responds to queries using an XML schema, which contains a disclaimer footer. Your legal department is prone to changing the wording on it so it probably makes sense to take it from an external file, so that your templates (which are part of your deployed source code) are not modified. Such templates could look like this:

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!

If you’re interested in Integration and APIs, don’t miss CONNECT 2014 London – the event behind the integration revolution!

5 Ways an API is More Than An “API”

An API is not only a building brick, it’s also a projection of a product vision, based on internal assets you can open to the world. Get ready for your next conversation when someone asks, “so what does API stand for?”


Governments Can Bridge Costs And Services Gaps With Sensor Networks

Governments are implementing sensor networks to streamline processes, cut labor costs and improve services. But extracting true value from these networks requires integration.

We’re happy to announce the release of Anypoint Studio July 2014 and ESB 3.5.1.  The Anypoint Studio release now contains support for finding Anypoint Templates to help you rapidly integrate systems as well as many usability and productivity improvements. The July 2014 release of Anypoint Studio also contains the Mule ESB 3.5.1 release, which builds on the 3.5.0 release with many bug fixes.

Anypoint Studio July 2014

The July 2014 release Anypoint Studio release contains many improvements targeted at improving your productivity on Anypoint Platform.

Anypoint Templates browser

You can now find Anypoint Templates, templates built to address the most common integration use cases and to help you get successful on Anypoint Platform quickly. You can access the templates by clicking the library button on the toolbar at the top left of Studio.

sumit.sharma on Wednesday, July 16, 2014

The Real World Cup Winner: APIs


What a world cup! I do feel bad for 50% of the MuleSoft team though (given that we’ve got a big office in Buenos Aires). It’s exciting though, because this was a very exhilarating competition that truly reached a fever pitch here in the US where “football” is traditionally a game with pads, helmets, and ball that doesn’t really roll.

What was really interesting was how this was truly a, “World Cup powered by APIs.” World Cup organizer FIFA has stated that more than a billion fans worldwide accessed information about the tournament through its digital platforms. I personally watched many games on my mobile phone, my tablet, and on my laptop. In fact, I distinctly recall being in the middle of a long line and putting on the Brazil – Columbia game that was streaming over a 3G network in San Diego.

“This has been the first truly mobile and social World Cup”

- FIFA president Sepp Blatter.

By unleashing your digital assets, flock to consume the digital mana, creating new value for consumers in the API age. The proliferation of both open and closed APIs has created a rich diverse ecosystem which is driving the Internet of Things (IoT) from an idea to a reality. But how do you get the most out of your existing APIs, and/or create new ones nimbly? How do application developers benefit by leveraging them? Can you predict it?

As an example, a good poker player uses the behavior and actions of the other players combined with his own hand and stack of chips  to his/her advantage. This combination of statistical and behavioral “” boost the value of every chip in his/her possession. Without using his/her environment, the intrinsic “value” of his current bank is significantly reduced.

In order to understand how this same philosophy applies to API design, let’s take a step back and look at the lifecycle of an API.

API Development Lifecycle

At Apple’s recent Worldwide Developers’ Conference (WWDC), Craig Federighi, SVP of Software Engineering, Apple, explained the driver for Apple Health and Healthkit as the need for greater interoperability between systems. He said, “Up to now, the information gathered by those (health) applications lives in silos … You can’t get a single, comprehensive picture of your health situation.”

Craig, we couldn’t agree more!

Sure, the continuing development of wearable devices promises a future in which all of us will have a better understanding and ultimately greater ownership of our health. It is a future in which providers are able to extend the point of care beyond the four walls of the hospital ward and monitor patients in real-time, wherever they might be.

Tackling API development with an API first approach allows companies to focus on designing APIs to deliver business, rather than focusing on the nuts and bolts of implementing those APIs. With design, businesses can create an application programming interface optimized for adoption and once finalized, use a platform to rapidly implement it by connecting it to backend services. Moreover, teams can work on various elements of an API solution simultaneously, ensuring all that it meets your technical and business expectations.

Starting with an API description is core to this API first approach – a clearly written service description makes it much easier for team members to collaborate from the very beginning. API mocking enables your team to build tests, clients and the server implementation for your API in parallel. From designing to building, to management and testing, approaching application programming interfaces with an API first strategy is crucial to creating successful APIs.

Netflix has decided to shut down public API support for third-party . An interesting decision, and in my a bad one.

Launched six years ago, the Netflix API provided developers a way to access content from their streaming and DVD catalog. That helped the company grow and gave developers a way to build new experiences around Netflix content (for example Flixster).

Last year the company said it would stop issuing new API keys to developers and last Friday they announced that their API will stop working on November 14th for most developers, except a few key partners and applications.

Even as SaaS adoption explodes and business processes move to the cloud, organizations still have crucial data locked in on-premises and legacy systems, and they aren’t going anywhere.

More and more companies are seeking new integration strategies to deal with these hybrid environments, and struggling with how and where to integrate them. This Thursday, join MuleSoft’s Chris Purpura, VP of Cloud Integration and Dan Diephouse, Director of Product Management, for a live webinar, “Top 3 Considerations for Integrating Hybrid Environments“, where they’ll give guidance to help you form a hybrid strategy.