Tag: CloudHub

Mariano Gonzalez on Tuesday, March 25, 2014

Batch Module Reloaded

0

With ’s December 2013 release we introduced the new batch module. We received great feedback about it and we even have some users happily using it in production! However, we know that the journey of has just begun and for the Early Access release of Mule 3.5 we added a bunch of improvements. Let’s have a look!

Support for not Serializable Objects

A limitation in the first release of batch was that all records needed to have a Serializable payload. This is so because batch uses persistent queues to buffer the records making it possible to processes “larger than memory” sets of data. However, we found that non Serializable payloads were way more common that we initially thought. So, we decided to have batch use the Kryo serializer instead of the Java’s standard. Kryo is a very cool serialization library that allows:

  • Serializing objects that do not implement the Serializable interface
  • Serializing objects that do not have (nor inherit) a default constructor
  • It’s way faster than the Java serializer and produces smaller outputs

Introducing Kryo into de project did not only made batch more versatile by removing limitations, it also had a great impact in performance. During our testing, we saw performance improvements of up to 40% by doing nothing but just using Kyro (of course that the speed boost is relative to the jobs characteristics; if you have a batch job that  spends 90% of its time doing IO, the impact in performance won’t be as visible as in one that juggles between IO and CPU processing)

Today I will introduce our performance test of the 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 module will automatically store all the data with CQS (Cloud Queue Storage) to achieve the expected resilience.

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 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!

Release 34 is now live! With this release we’ve made a number of improvements to to make managing your integrations easier. These include the ability to promote applications from sandboxes, monitor workers for problems, create secure environment variables, and scale applications vertically, as well as horizontally.

In the past, as now, ESB follows a release schedule that introduces a new version of our industry-leading ESB software every 9 – 12 months, supplemented with maintenance releases approximately every 6 months. Though this cadence fit very tightly with the demands of our customers who deploy Mule on premises, we came to realize that our customers deploying Mule to were much more flexible in terms of updating versions of software, and were more eager to take advantage of new features and functionality.

0

Just when you thought it couldn’t get any better, it got better. Dataloader.io, the most popular Salesforce data loading solution on the AppExchange now supports importing and exporting of files to and from Dropbox!

dataloader.io and dropbox

Data loading aficionados can now quickly and easily import or export data directly to and from their Dropbox account. By simply entering your Dropbox credentials, users can make Dropbox their source for CSV files. Similarly, exporting to Dropbox is as easy as choosing Dropbox as your connection and destination folder from a tab. Then, by following the standard steps to import and export data with dataloader.io, you’ll be up and running in no time – it’s that simple!

Ross Mason on Monday, July 29, 2013

Raspberry Pi gets an API

0

In the Internet of things no device is an island. And while Raspberry Pi devices are pretty cool on their own adding an API makes them a lot more interesting. We have been playing around with Raspberry for a while now and have a small distribution of , called ‘ Edge’ that happily runs on small embeddable devices like the Raspberry Pi.  These ARM-based devices are taking the world by storm since they are lower powered, low cost and can be embedded into small hubs to control other things like lightbulbs, or be used inside anything from PoS kiosks to gas pumps to cars to medical devices.

You may have read about our mountain trek, new release cycle, and the increased pace of delivering. We’ve  climbed our first mountain and we’re happy to announce the availability of our first release in our trek: Andes! This delivers major usability improvements around our platform, new connectivity to applications such as Marketo and ZenDesk, and expanded API management capabilities. We’ll summarize what’s new for you here and we’ll be doing deeper dives over the coming days for you to learn more.

Lack of Connectivity Limits Marketing and Sales Engagement with Customers

As more companies adopt sales and marketing applications, providers are under the gun to create and offer functionality that supports the business process and automation requirements of these individual and sometimes silo teams.  In any given organization, sales and marketing use upwards of 10 – 15 applications to engage, onboard and maintain customer interactions.  Believe it or not, here at MuleSoft our marketing and sales teams use over 30 different applications. Yes 30, and we have less than 30 people in our marketing organization! Sample applications include, HootSuiteGoogle Apps, Confluence, Yammer, Salesforce, SurveyMonkey, WebEx Events, Eventbrite, Cloud9 Analytics, KISSmetrics, Google Adwords, GetSatisfaction and the list goes on. Each of these applications are used to engage the customer in a different stage of the buying process:

 

At MuleSoft, we’re constantly looking for better ways to solve the integration needs of enterprises. Software as a service is creating new integration requirements and Gartner expects the market to continue growing at a blistering pace of 17.9% through the end of 2013. With the adoption of in Europe and Asia Pacific accelerating, we talk to customers every day looking to integrate in the cloud across geographies, and isolate certain data to comply with data protection laws.