Advanced Mule Concepts

Standard Support for Mule 4.1 ended on November 2, 2020, and this version of Mule will reach its End of Life on November 2, 2022, when Extended Support ends.

Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted.

MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements.

After you become familiar with the basics of Mule application development and Mule runtime engine (Mule) concepts, you can focus on more advanced features, such as the execution engine, the classloading isolation mechanism, and distributed file polling.

Learn about the execution engine to understand how Mule runtime engine processes the operations in a Mule application flow, and to understand how to change the thread pools if needed. Mule runtime engine uses execution metadata provided by operations in a flow to perform autotuning.

The classloading isolation mechanism implemented in Mule 4 is designed to make upgrades easier by preventing components from exposing their internal resources. All components interact with each other through their defined APIs so that only exposed resources can be accessed by other components. Classloading isolation ensures that a component’s internal content is protected and can be changed any time, without affecting other components.

Mule 4 supports distributed file polling, which allows connectors to read files from certain directories as they are created. Distributed file polling also makes it possible to poll files in all cluster nodes.

Mule 4 also supports distributed locking, which provides the ability to create locks for synchronizing access to resources within Mule components.

You can refer to the Javadocs for Mule Kernel (the community edition of Mule runtime engine) to learn definitions for classes, fields, and data types.

You can see a list of third-party software that is included as part of Mule runtime engine as internal dependencies.

Was this article helpful? Thanks for your feedback!
View on GitHub