You, yes you, should attend an API-led connectivity workshop

September 11 2015

3 comments

Have you ever wanted to learn best practices from MuleSoft’s technical experts? Are you an architect, developer, or manager looking to implement your first MuleSoft use case? Want to experience a one-of-a-kind integration workshop AND have tasty cocktails?

Now is your chance.

If you’re in the Washington DC area on October 27, you can attend our API-led Connectivity Workshop and get hands-on experience with Anypoint Platform with MuleSoft’s expert team.

Getting Started with DataWeave: Part 2

September 10 2015

13 comments
Getting started with dataweave part 2

In the Getting Started with DataWeave: Part 1, we introduced you to DataWeave and its canonical format, the result of every expression you execute in the language. We now continue to explore our new transformation engine, aiming to give you enough grounding to tackle real-world use-cases.

As we did in Part 1, we will continue to show the results of each expression in the DataWeave canonical format.

Want MuleSoft training? Enroll in MuleSoft.U!

motif

Introducing MuleSoft.U

icon-muleears-blue-bigicon-muleears-blue-big

Ever wanted to get certified on our Anypoint Platform, but discovered that you didn’t have the training?

We’d like to introduce MuleSoft.U: self-study, public, FREE certification courses that will enable developers to learn core MuleSoft skills. At a significant cost per seat for a public class, instructor-led training is unattainable for most independent developers. With MuleSoft.U, independent developers can get up and running in no time.

Fast and Slow through the Air

motif

Handling endpoints with disparate speed when the platform is in the cloud

A fairly common integration requirement is to accumulate data coming in real-time or near real-time, hold and consolidate the records, then send the transformed messages to another system on a fixed schedule (e.g. daily etc.) for business reasons, especially if the endpoints are legacy systems. For on-premises integration platforms, this use case is rather straightforward to implement.

Object Lifecycle and Dependency Injection in Mule 3.7

motif

Howdy! This is the last post of the Mule 3.7 series Be sure to check out the other posts in the series:

IMPORTANT: If you haven’t read the previous posts in this series, do so now. This will be very difficult to follow otherwise.

JMS Queue: When Size Does Matter

motif

Anypoint Platform is fast. The legacy systems that it often connects to? Not so much.

Therefore, in real world use cases, the requirements often call for limiting the message throughput to protect the endpoint systems from being overwhelmed by traffic. Architectural designs that support message throttling commonly incorporate some elements of message queues to stage and hold messages in-flight, so that the endpoints can process them at a steadier pace.

So you want to set up an API strategy. Now what?

motif

Upcoming webinar: So you want to set up an API strategy. Now what?

Join us for the latest installment in the MuleSoft webinar series as we sit down with Julie Craig, Research Director at Enterprise Management Associates, and Reza Shafii, Director of Product Management, MuleSoft to discuss some of the common pitfalls and questions businesses have when developing their API strategy. Craig and Shafii will talk about the essentials of an API-led approach to design,

One to contain them all: Unifying the Mule Registry in 3.7

motif

In this post we’re going to continue the discussion started our last post “A sneak peek into Mule 3.7’s deepest internals” about how Mule’s registry, lifecycle and dependency injection mechanism are being overhauled in Mule 3.7. In this case, we’re going to take a deep dive into how we managed to unify the registries while keeping backwards compatibility and all the implications of such maneuvers.

A sneak peek into Mule 3.7’s deepest internals

motif

Mule 3.7 is approaching, and among other things we decided to put a lot of focus on the experience of the guy coding custom components (Devkit based or not). For this, the first 3.7 milestone is incorporating big changes in terms of the how Mule Lifecycle and Dependency Injection are applied.

As I said, these changes are BIG, so for clarity reasons we’ll cover them in a series of post starting with this one.

API Implementation: Using Idempotent Filter to Prevent Message Twinning

motif

Twinning can be evilTwinning can be evilWhen it comes to API implementation, message “twinning” is one of those annoying pitfalls that in the worst case scenario, can lead to major problems downstream, such as duplicate orders being submitted etc. However, the client side is often not equipped to prevent duplicate messages from being sent, especially for javascript based user interface calling REST APIs, where user actions such as fat-fingering and unintentional double-clicking are virtually impossible to control.