Wednesday 20 March 2024

List out the primitives used in mediation. in MuleSoft 165


List out the primitives used in mediation. in MuleSoft 

In MuleSoft 4, the concept of mediation primitives has been replaced by a more modular approach to flow design. However, there are still essential components that serve similar purposes to the old primitives. Here's a breakdown of some frequently used components for message processing in Mule 4:

Message manipulation:

  • Message Transformer: Enables modifying the message payload using DataWeave or other languages.

  • Record Transformer: Specifically designed for transforming record-structured messages.

  • Content-Based Router: Routes messages based on content criteria like payload elements or headers.

Message routing:

  • Choice: Routes messages based on a specific condition evaluated by an expression (similar to Message Filter).

  • Split: Splits a message into multiple messages based on a delimiter or expression (similar to Fan-Out).

  • Scatter-Gather: Sends messages to multiple destinations and waits for responses before proceeding (similar to Fan-Out/Fan-In combination).

External interaction:

  • HTTP Request: Makes HTTP requests to external services.

  • JDBC Connector: Connects to and interacts with relational databases.

  • JMS Connector: Sends and receives messages from JMS queues and topics.

Other essential components:

  • Async: Enables asynchronous processing within a flow.

  • Enrich: Enriches the message with additional data from external sources or expressions (similar to some primitive operations).

  • Logger: Logs messages at various points in the flow for debugging and monitoring.

Remember: These are just some of the core components used for message processing in MuleSoft 4. You can find a comprehensive list of available components and their functionalities in the MuleSoft documentation

No comments:

Post a Comment

Note: only a member of this blog may post a comment.