Mule application architecture: 1. About mule

Document directory

• About mule Application Deployment

Mule application architecture

Kimmking

2012-12-6

This article describes the features of the mule structure. You can use them to build your mule application.

L about mule

L about mule execution units

L about stream

L stream architecture

L substream

L stream Configuration

L advanced Use Cases

 

About mule

Mule ESB provides integrated application integration that can serve both small business companies and large enterprises. As the core function of mule, the Enterprise Service Bus (ESB) facilitates Intranet connections within the Organization and external connections between web-based APIs and other cloud resources.

 

All mule applications-and their cloud-based distant peers, such as iapps-are easy to create because they support being designed to be pluggable (plug in) the standard interface provided by the mule service bus is pre-packaged to build a module.

 

The studio interface provides powerful drag andgrop design graphics and Application Builder ). The corresponding XML editing environment provides a lot of convenience for developers who directly edit code.

 

You can deploy a mule application to a robust and lightweight mule server. It performs just as well in standalone installation and cluster topology mode. The management console can be deployed to a mule repository or multiple mule clusters consecutively.

 

Cloudhub (mule ion) provides a platform to quickly install applications on the cloud.

 

The powerful datamapper feature not only converts loads from one data format to another, but also remaps data fields and filters, enhances, and routes loads in a variety of complex ways.

 

The Data Loader option reduces the pain and uncertainty of uploading large amounts of data to the web API server (such as Salesforce and SAP.

 

There are a large number of free or paid ctor INS that support your mule application to quickly and easily implement cloud-integration ).

 

About mule applications

Generally, when a mule application receives a message, it processes the message in the order it receives the message. Such processing may lead to different results. Sometimes, the mule application returns a modified or replaced message to the original message source. In addition, applications can send messages to one or more third-party applications in the original or modified format. In other cases, if a message does not conform to a specific standard, mule can reject it.

Complex mule applications can achieve message processing far beyond this linear method. Advanced mechanisms can process different messages in different ways. In addition, you can build your application and use:

L multiple queue and thread protocols to maximize Throughput

L transactions or cluster nodes to maximize reliability

L object storage to ensure data persistence

These are only a small part of the functions that you can implement with the mule application.

About mule Application Deployment

You can deploy the mule application in the following three ways:

As a zipped compressed file (including the mule application and all code resources and configuration information), run it on an application server (such as a mule ESB independent server.

Deploy it to the mule repository, And you can manage it on the mule console. In this way, you can deploy a mule application to the mule cluster topology.

Deploy to cloudhub platform (mule ion)