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.

It sounds like the title for a fantasy movie, but Google, OAuth and the “confused deputy” is a very common issue. Wikipedia defines a confused deputy as “a computer program that is innocently fooled by some other party into misusing its authority. It is a specific type of privilege escalation” (complete article here).

The Wikipedia article shares an example of a compiler exposed as a paid service. This compiler receives an input source code file and the path where the compiled binary is to be stored. This compiler also keeps a file called BILLING where billing information is updated each time a compilation is requested. If a user were to request a compilation setting the output path to “BILLING”, then the file would be overwritten and the billing information lost. In this case, the compiler is a “confused deputy” because although the client doesn’t have access to the file, it’s tricked the compiler (who does have access) into altering the file.

When looking at options for your next generation integration platform, the development language of the underlying ESB should not be a primary concern. .NET teams in particular often constrain their search to only .NET-centric ESBs, ultimately leaving them few options. If you find yourself in this position, here are a few things to consider:

  • At its core an ESB is all about interoperability.
    A strong ESB will support a broad range of standards, protocols, and adapters, enabling integration of services and applications written in any language or platform. A Best of Breed ESB doesn’t care if the services it is connecting are written in Java or C#.
  • A Best of Breed ESB will enable the majority of integration work to be done through tools that are easy to learn and provide visibility into what is happening in the ESB, rarely requiring developers to write or debug code.
  • When code is required for customizing integrations, the ESB should provide frameworks, APIs, and templates for the customization. So, for example, a .NET developer customizing a good Java-based ESB would use a small subset of Java, primarily needing to understand Java syntax, not the full breadth of Java technology. A Best of Breed ESB should also be extendable with other familiar languages, such as JavaScript or Python.
  • Java and C#, the predominant languages in the enterprise, are nearly identical in syntax.

So how should you choose the best ESB solution? As you begin the journey to evaluating your next generation integration platform there are critical components that will help you connect, implement, and deploy faster:


At MuleSoft, we’re fortunate to have the opportunity to work on one of the most meaningful challenges in integration: interoperability across healthcare IT systems. Whether it’s ensuring that doctors have the information they need to make an accurate diagnosis or verifying a patient’s prescription so that they have access to medication, integration is core to a functioning health care system (indeed integration is often the root cause when there are problems, as those at Healthcare.gov can attest!).

HIMSS, the largest healthcare technology conference in the US, is where the two worlds of ‘today’ and ‘tomorrow’ meet, as the who’s who of the healthcare world gather to learn, share and inspire each other to achieve more.

The recent growth of SaaS applications, systems, and services in the market has greatly impacted how we approach enterprise architecture. Data now resides beyond the enterprise firewall and needs to be controlled and managed – a problem made increasingly difficult by the growing popularity of bring your own device (BYOD) policies.

Hybrid integration bridges the network divide between existing enterprise databases, warehouses, applications, legacy systems and SaaS, B2B, B2C, BYOD, and big data. It leverages new systems to make way for innovation, competitive advantage, and driving new business models, allowing on-premise applications to seamlessly integrate with cloud based ones. MuleSoft helps enterprises connect applications both on-premise and in the cloud, simplifying the integration process and allow for seamless hybrid integration.

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!

Why the Internet of Things Is More 1876 Than 1995

Looking back into history helps us understand our present and future. The Industrial Revolution hit its critical mass in 1876. The Internet of Things has hit that point today.


Enterprise Security Professionals Identify Mobile Computing Security Challenges

It’s clear BYOD has changed enterprise IT, but that doesn’t make it any less of a security nightmare. Data security, security policies, and integration top the list of problems.


Our Muley this week is our reigning Team Work Award winner! From running around the office at super speed to helping build the amazing talent base at MuleSoft, she has left an impression on every Mule.  Meet Mae Limskun – Recruiting Coordinator extraordinaire and future Britney Spears backup dancer.

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

  • Is it morning already? Felt like I just went to bed 10 minutes ago!

What exactly do you do?

  • Coordinate interviews (onsite and remote) for candidates in the US, Australia, and London; drive interview process/pipeline, and ensure an exceptional candidate experience.

How did you first get interested in your field?