DataWeave performance demystified

dataweave

I have been asked so many times about DataWeave Performance during my time in the field. This is because developers try to find arguments to not use it when they realize that a new and proprietary programming language is introduced. Most of the time they have the same “natural response” of resolving the problem by going to the known and comfortable zone called “Java.”

Stop making spaghetti code

Spaghetti is delicious when it’s on your dinner plate, but it can give you indigestion when it’s an enterprise integration pattern. When developers and IT teams are tasked with building integrations, creating too many point-to-point integrations can create an ugly mess that’s brittle, expensive to maintain, and difficult to modify or adapt. This has negative effects on enterprise agility and efficiency.

MuleSoft_SOTW_new_2-02 (1)MuleSoft_SOTW_new_2-02 (1)

James Donelan, our VP of engineering, has an article in Techbeacon this week in which he outlines the risks of messy point-to-point enterprise integrations.

MuleSoft at MuleSoft: Anypoint vs. Custom Code Automation

There are numerous great reasons for using Anypoint Platform at MuleSoft. You might even assume that inside the company there would be little competition. But like many organizations, using Anypoint here required competing with the inherent desire people have to use custom code for integrations.

Custom code integrations have a natural gravity to them. The practice generally starts with the desire to satisfy curiosity about how using a service could be automated with an API and diving in with a common toolset such as Python,