Enterprise Integrations Patterns

Ballerina usage patterns and best practices for implementing enterprise integrations. These patterns are based on the Enterprise Integration Patterns book by Gregor Hohpe and Bobby Woolf. Each sample is a simplified version of a real-world integration scenario.

Content Enricher

Add data to message

Content EnricherMessage ChannelMessage EndpointMessage

Content Filter

Remove data from message

Content FilterMessage ChannelMessage Endpoint

Document Message

Transfer data to another application

Document MessageMessage ChannelMessage EndpointPoint-to-Point ChannelRequest-Reply

Message Router

Route messages to different output channels

Message RouterMessage ChannelMessage EndpointMessage

Message Sequence

Send large data sets in chunks

Message SequenceMessage ChannelMessage EndpointMessage

Message Store

Capture message information in a central location

Message StoreMessage ChannelWire TapMessage EndpointMessage

Messaging Bridge

Connect messaging systems

Messaging BridgeMessage ChannelMessage EndpointChannel AdapterMessage

Normalizer

Process messages with different formats

NormalizerMessage ChannelMessage EndpointMessage TranslatorMessage RouterMessage

Scatter-Gather

Send messages to multiple recipients and re-aggregate the responses

Scatter-GatherAggregatorMessage ChannelMessage EndpointMessage RouterMessage

Wire Tap

Publish to a secondary channel for inspection

Wire TapMessage ChannelMessage Endpoint

Subscribe to our newsletter

Subscribe via RSS

In the creation of Ballerina, we were inspired by many technologies. Thank you to all that have come before us (and forgive us if we missed one): Java, Go, C, C++, D, Rust, Haskell, Kotlin, Dart, TypeScript, JavaScript, Python, Perl, Flow, Swift, Elm, RelaxNG, NPM, Crates, Maven, Gradle, Kubernetes, Docker, Envoy, Markdown, GitHub, and WSO2.