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

Free Resource

Share, secure, distribute, control, and monetize your APIs with the platform built with performance, time-to-value, and growth in mind. Free 90-day trial of 3Scale by Red Hat

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

Explore the core elements of owning an API strategy and best practices for effective API programs. Download the API Owner's Manual, brought to you by 3Scale by Red Hat

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

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

{{ parent.tldr }}

{{ parent.urlSource.name }}