Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Intro to Mule ESB and the Elegant 'Endpoint' Data Channel

DZone's Guide to

Intro to Mule ESB and the Elegant 'Endpoint' Data Channel

· Integration Zone ·
Free Resource

The State of API Integration 2018: Get Cloud Elements’ report for the most comprehensive breakdown of the API integration industry’s past, present, and future.

This is a core concepts example that demonstrates how to invoke a Mule application using HTTP. The example introduces two key concepts in Mule:

  • Flow - A Mule flow is a flexible way to build integrations by simply choosing building blocks from Mule's wide range of functionality and gluing them together.
  • Endpoint - An endpoint is a channel to receive or send data in Mule. An endpoint has a specific protocol such as HTTP or JMS and a set of elements for configuring filters, transactions, transformations and more. There are 2 types of endpoints: inbound or outbound. An inbound endpoint allows a flow to be called by an external client. In this particular example, we will use an HTTP inbound endpoint, but most endpoints in Mule can be used for inbound and outbound communication. Conversely, an outbound endpoint is used to publish data to a service, application or resource.


    Read more in the Mule Endpoint Docs

Your API is not enough. Learn why (and how) leading SaaS providers are turning their products into platforms with API integration in the ebook, Build Platforms, Not Products from Cloud Elements.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}