This blog was originally published on the Salesforce blog and was co-written with Ed Cho, Senior Product Marketing Manager on the Platform team.
Cutting doctor’s appointment referral times by half. Processing a bank loan in support of small business in less than two days. Accelerating test results to help stop the spread of disease. IT teams have always been implementing, maintaining, and governing a number of high-demand applications and systems.
A few years ago, Gartner predicted the emergence of the Citizen Integrator: a domain specialist without an engineering background. They would use “clicks, not code” to integrate software applications and perform integration tasks as a whole, without differentiating the processes of integrating data from applications.
They are focused on automating business tasks and on business outcomes building integrations. They see integration as a tool to achieve those
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.”
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.
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.
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,
Have you ever tried to move already created elements through the canvas in Mule Studio? Well, if you did, you may have figured out that the elements weren’t moved at all. You would probably have seen a black box while you were dragging elements into the canvas and nothing else; the elements were not transported.
Drag and drop support is important because when users use a tool like Mule Studio,