Geek Answers Handbook

The difference between mule connectors and vehicles

I am trying to evaluate the set of ready-made vehicles provided by Mule and compare them with offers, for example. ServiceMix and OpenESB.

On the Mule homepage, I will find a list of supported transports at:

http://www.mulesoft.org/documentation/display/current/Transports+Reference

However, I also find a list of Connectors at:

http://www.mulesoft.org/connectors

It seems that there is some overlap between these lists, but some technologies are listed as transports and not as connectors, for example, there is a quartz transport, but not a connector.

So, the question is: what is the difference between a mule transport and a mule connector, and why is it, for example, Quartz transport, and not a connector?

+3
source share
2 answers

Transports are aimed at a method of transporting data, that is, a protocol such as HTTP or reading / writing files. These are general concepts, and the other side behind such a data channel can be anything, a pure data receiver or a party with which you can exchange data, your own company or another.

Connectors are designed to use certain APIs, for example. those from salesforce.com or facebook. Typically, the choice of connector also determines how the data will be transmitted at the end, for example. HTTP

From mulesoft.org:

, . , (, JDBC, FTP, HTTP, POP3 ..) API, Salesforce Twitter.

+7

( ) Mule Mule. . , , , . , HTTP- , HTTP Mule HTTP-.

, . , , Mule .

0

More articles:


All Articles