MUnit 1.0 Release Candidate

studio

We’re happy to announce the 1.0 release candidate of MUnit – the unit and functional test framework for Mule. This is our first official release of MUnit and incorporates major usability improvements, broader support for Mule components and many bug fixes.

Anypoint Platform API offering – June 2015 release

motif

Anypoint Platform API offering – July 2015 release

I am happy to announce that as part of the Anypoint Platform June launch we introduced the following Anypoint Platform API offering capabilities that together enable significant efficiency and user experience boost for Anypoint Platform users.

Let’s dig into each of these areas.

Anypoint Platform June 2015: Launch Wrap Up

studio

Today, the Mule 3.7 runtime and Anypoint Studio June 2015 are now GA. This release brings to a close over two months of product announcements impacting nearly every aspect of Anypoint Platform. It also marks the beginning of a new way for our user community to experience our products — less as a collection of rich independent capabilities and more a unified platform with unified tooling and unified management to help users deliver value with speed, scale, and control.

Monitor RAML APIs with API Science

RAML

At MuleSoft we truly believe in the power of RAML as a contract for APIs. RAML allows teams to quickly and easily define, build and collaborate on APIs. Our Anypoint Platform for APIs is built from the ground up to easily manage RAML based APIs by providing a simple RAML API proxy as well as an easy to use RAML API Console.

Introducing Pub/Sub Pattern for Anypoint Templates

motif

Anypoint Templates showcase best practices around most common data integration patterns between two systems, for example, Salesforce and Workday, Salesforce and MS Dynamics CRM, Salesforce and NetSuite, Workday and ServiceNow and so on. With our new series of Pub/Sub templates, implemented using a publish/subscribe architecture, we are providing a more modularized approach to integration by allowing you to decouple source and destination systems and easily incorporate multiple systems without having to modify the existing integration application.

Refactoring MUnit: the Mule testing framework

unit-testing

A few years ago, a MuleSoft engineer had a vision. That vision: automated testing for Mule applications in Anypoint Studio. As this developer’s focus was building Mule applications to connect SaaS apps, a validation framework would significantly reduce development time and increase productivity across teams. More specifically, unit tests would allow this developer to mock dependencies, uncover problems early, refactor applications quickly, and provide agile documentation for other Muleys. Months later, MUnit was born.

Salesforce Connector June 2015 Release: What’s New

Mulesoft-salesforce

We are happy to announce the June ’15 release of the Salesforce Connector v6.2.1. With this release, we now support 56 different operations across multiple Salesforce APIs including the Apex REST API. This release also includes significant authentication capabilities such as OAuth v2.0 JWT bearer token and OAuth v2.0 SAML bearer assertion.

The Fastest and Easiest Way to turn WSDLs into a Reusable Connector

mulesoft-plus-anything

Can MuleSoft connect ________ (insert name of any system) to ________? Regardless of how you’ve filled in the blanks, anyone from MuleSoft will answer with an enthusiastic, ‘Yes, we can!’

To enable this universal connectivity, along with increasing the breadth and the quality of our out-of-the-box connectors, we are continuing to invest in expanding the usability and feature set of our connectivity tooling, including our: HTTP Connector, Web Service Consumer, and our SDK, Anypoint Connector DevKit.

Developer Spotlight: How We Built Stock Cars

motif

 

This post is the first in a three-part series covering the projects we built and had on display at our first Integration of Things Zone at CONNECT 2015. Missed us there? No worries, not only will you get a sense of the cool IoT projects we built below, you’ll also get a front row seat as to how we built it, and with what technologies. So put on that seat belt, and learn about how the team built Stock Cars, a project that brought big data to life by mashing Anki Drive cars with stock market data from NASDAQ.

Why we built it

Stock Cars was the product of an IoT themed internal hackathon we ran at MuleSoft in April. For the greater part of a weekend, engineers from Buenos Aires to San Francisco teamed up to bring projects we cared about to life. The team consisted of four people: Victor Romero, Alejandro Sequeira, Alejandro Nosenzo and myself.

Our goal was to highlight, with a simple Mule application example, how you can connect different technologies to create new and innovative use cases. We chose Anki Drive Cars, an increasingly popular game that you can buy online or at places like the Apple Store, as our 3rd party device to interact with because we realized, with minimal digging, that you could program your own games using their custom SDK!

API-led connectivity and CQRS: Aligning business & IT with RAML

RAML

Part 2: Building a Data Query Application

In a previous blog, we talked through how you might design a solution to deliver a Command Query Responsibility Segregation (CQRS) pattern with Anypoint Platform. In this blog, we’ll discuss how an API-led connectivity approach can help you deliver this pattern (and the mobile application your business is demanding) with speed and scale while maintaining control over your critical data assets.

 

API-led connectivity and API design

api-led-connectivity-design