Mule Basics Flashcards
MuleSoft
Java based Enterprise Service Bus (can be deployed anywhere). Decouples point-to-point integration (apps talk to ESB, not directly to each other).
Mule Runtime
the engine for Anypoint Platform. Mule apps are deployed to a Mule runtime.
Mule Event
An event source receives a trigger (http, jdbcs, ftp, jms) and creates a corresponding mule event object and forwards the processing.
Mule events are immutable. Any change to an instance of a mule events results in the creation of a new mule event instance.
Mule Message
Connector operator receive and return mule messages. I.e. When a listener receives a HTTP request, it creates a mule message with the HTTP body as the payload and sets HTTP headers and other metadata in the attributes.
Variables
are used to store messages, attributes, or payload as an object number or string
RAML
language designed to describe a restful API.
API
provides a way of communicating with a software component. It allows functionality to be independent of implementation.
API proxy
app that controls access to a web service through an API gateway.
Web service
method that allows two software systems to exchange data over the internet,
SOAP web services
archaic, communication rules are defined in XML.
Rest
similar to SOAP but uses HTTP protocols.
DataWeave
language for formulating expressions in mule. DataWeave uses Transform Message (script) core component to access access, manipulate, transform, and extract data from a Mule event.
Batch Processing
useful for streaming input or for performing near real-time data integration between Saas.
Mule Components (three of them)
core components, connectors, and modules
Core Components
core functionality of mule runtime (logging, setting payloads, transforming messages, try catch, batch processing)