Today I am going to introduce a recently created module: Mule Requester.

As its name may hint, its goal is to allow the request of a resource at any point in a flow. This resource can be a file, a message (from VM, JMS, AMQP, etc.), an e-mail, etc. It’s intended for resources that originally could only be requested by message sources.

Let’s try to explain it better with an example. Say we want to consume messages from a queue on demand, i.e. not consuming the message as soon as it’s put on the queue but at a later stage, when a user calls an HTTP inbound endpoint, for example. We cannot achieve this by using a JMS inbound endpoint, since it will consume the message as soon as it’s put on the queue. Thinking about a way of doing this, we could have a stopped flow and activate it on demand but this would cause the consumption of more than one message or a clumsy implementation that would pick a message and stop the flow again. Another option would be to use a component but this would have to deal with the specifics of the transport, leading to either one implementation per transport type or a big component handling all the transports.

The above mentioned case can be easily achieved using the Requester module, simply by placing the starting point of the flow (the HTTP inbound endpoint in our example) followed by the requester:

Today I will introduce our performance test of the Batch Module introduced on the Mule’s December 2013 release. I will guide you through the test scenario and explain all the data collected.

But first, if you don’t know what batch is, please read the great Batch Blog from our star developer Mariano Gonzalez, and for any other concerns you also have the documentation.

Excited? Great! Now we can start with the details, this performance test was run on a ’s Double worker, using the default threading profile of 16 threads. We will compare the on-premise vs cloud performance. Henceforth we will talk about HD vs CQS performance. Why? On-Premise and CloudHub users will be using by default the HardDisk for temporal storage and resilience but, this is not very useful on CloudHub as if for any reason the the worker is restarted, the current job will loose all its messages, then if  Persistent Queues are enabled the Batch module will automatically store all the data with CQS (Cloud Queue Storage) to achieve the expected resilience.

Skip the hampers and gift cards and give the developers on your team something useful this holiday season to transform their hard-earned skills into something creative.


Raspberry Pi

Way better than Fruitcake, Raspberry Pi is a credit-card-sized single-board computer running Linux that can be used for all kinds of great ideas from running a web server in your pocket to building home automation systems. We used one to fly helicopters using a fitness wristband device at our last MuleSoft hackathon. You can get one here for less than $50.

This week we’re wrapping up our Meet a Muley posts for 2013 with James Hall! As an Interaction Designer on the Product Team, James focuses on creating the best possible experience for our users. Read on to learn why he considers himself a “shaved ice connoisseur” and how he deals with being a tech-neophyte in a tech startup!

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

  • Did 6am always feel this early?

How did you find MuleSoft?

  • I knew I wanted to relocate to the Bay Area, so I started searching for well funded companies with huge growth trajectories. MuleSoft surfaced through CrunchBase, and I thought the story was very interesting. I really wanted to develop my technical understanding and MuleSoft felt like it would provide a great education.

We’ve all been there. Sooner or later, someone asks you to periodically synchronize information from one system into another. No shame to admit it, it happens in the best families. Such an integration should start with getting the objects that have been modified since the last sync (or all of them in the case of the very first sync). Sure, this first part sounds like the easiest of all the sync process (and in some cases it actually is), but it’s not without its complexity. Step by step you need to:

  • Go into a persistent store and grab the timestamp for the last update
0

Companies are adopting a variety of SaaS applications to meet their business goals but are ending up with a highly fragmented ecosystem. At the same time, customers are interacting with businesses across an increasing number of channels, including websites, numerous social media platforms, call centers, in-store and more. With so many customer touchpoints, optimizing engagement and having a single view of your customer data across all applications, devices, and interactions is crucial. Many businesses are interested in becoming customer companies and improving service and support across all channels, but just don’t know where to start.

Fun Fact - Here at MuleSoft, we use nearly 80 applications!

The challenging part of adopting new SaaS applications is connecting them to existing applications and syncing data across a customer’s lifecycle to ensure a streamlined customer experience. If these applications are not connected, data remains siloed and companies fail to obtain a single view of the customer. An integration platform makes it possible to break down those silos, streamline processes, build a future-proof enterprise, and improve customers’ experience.

We are all very proud to announce that Mule’s December 2013 release shipped with a major leap forward feature that will massively change and simplify Mule’s user experience for both SaaS and On-Premise users. Yes, we are talking about the new Batch jobs. If you need to handle massive amounts of data, or you’re longing for record based reporting and error handling, or even if you are all about resilience and reliability with parallel processing, then this post is for you!

This week’s Muley comes to us from Sweden! Albin Kjellin is our Solutions Architect in the San Francisco office, and as a part of the Services and Support Team, he spends much of his time solving problems with his technical expertise. When he’s not helping customers with their CloudHub needs, he’s refilling the coffee in his awesome Sweden moose mug. Read on to learn a little more about Albin!

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

  • I wonder if I can get away with not shaving for one more day.

How did you find MuleSoft?

  • I found MuleSoft a little bit by coincidence. My wife got a job at UCSF so we moved here from Stockholm and while waiting for the paperwork to process I found out that MuleSoft’s HQ was located in San Francisco. Since I had tested Mule ESB at my previous job to build integrations and had liked the product, I thought I would apply.

 

We’re excited to announce the Studio (December 2013) release! It includes a new Mule Runtime (December 2013), which introduces new batch capabilities for complex -like data integration tasks such as synchronizing SaaS and on-premise applications, flat file processing, and database reporting and synchronization. Also new in this release are Studio support for Mule expression language auto-completion, cron-expressions for poll scheduling and support for management of job schedules in CloudHub.

 

For this week’s Meet a Muley post, we’re switching things up a bit and introducing you to someone from the marketing team! Dan Ahmadi not only has the longest title in the company (Marketing Programs and Demand Generation Manager), he’s also a jack of all trades. He works across account development, product marketing and digital marketing teams, all to drive global demand generation initiatives and marketing operations.

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

  • That’s my face!