Spring Integration Highlights

28 Oct 2017

Spring integration is intended for enterprise message-driven architectures. It implements patterns described in the Enterprise Integration Patterns book. This document consists of highlights of interesting parts of Spring Integration documentation.

Comparison with functional programming

Message driven architectures have many similar abstractions to functional programming. See for example comparison with Java 8 Streams.

Spring Integration Java 8 Streams
Chain Pipeline
Filter filter function
Transformer map function
Splitter flatMap

One of main differences between is treatment of time e.g. Java 8 Streams don’t have equivalent method to Delayer. Java 8 Streams are not normally integrating with outside systems and are to finish immediately.


Combines multiple messages from single input channel into a single Message. Is stateful as messages have to wait in message store for each other. Most common usage is for messages to wait until a matching message (e.g. by correlation id) arrives or timeout. Is in a way opposite or Splitter.


Suspends certain message group and sends them out ordered correctly. Default implementation groups by header attribute correlation_id and sequences by header attribute sequence_number.


Sends a message to multiple recipients and then aggregates the replies. Recipients are registered by listing their channels. Replies are gathered from a single reply channel.

Thread Barrier

Suspends a message until correlating message arrives on separate channel or times out sending message to discard channel.

<int:barrier id="barrier1" input-channel="in" output-channel="out"

<int:outbound-channel-adapter channel="release" ref="barrier1.handler" method="trigger" />

Claim Check

Hides temporarily part of a message. Hidden data is stored separately and later claimed to be returned.

<int:claim-check-in id="checkin"
<int:claim-check-out id="checkout"

Channel Configuration

Channel Modes

Channel Types

Messaging Bridge

Connects two Message Channels or Channel Adapters usually providing some flow controlling functionality. For example connecting JMS with Email.

Metrics: Time-Based Average Estimates

Other than usual metrics the framework also offers interesting averaging method Time-Based Average Estimates. Averages corresponding to older messages are reflected less into the result. For example S(n) = sum(i=0 to n) exp(-i/M) x(i)/ sum(i= 0 to n) exp(-i/M) where x(i) is an average for a time slot i.

Monitoring: Integration Graph

Provides access to an application’s runtime object model which can, optionally, include component metrics. Example:

  "contentDescriptor": {
    "providerVersion": "4.3.0.RELEASE",
    "providerFormatVersion": 1.0,
    "provider": "spring-integration",
    "name": "myApplication"
  "nodes": [
      "nodeId": 1,
      "name": "nullChannel",
      "stats": null,
      "componentType": "channel"
      "nodeId": 2,
      "name": "errorChannel",
      "stats": null,
      "componentType": "publish-subscribe-channel"
      "nodeId": 3,
      "name": "_org.springframework.integration.errorLogger",
      "stats": {
        "duration": {
          "count": 0,
          "min": 0.0,
          "max": 0.0,
          "mean": 0.0,
          "standardDeviation": 0.0,
          "countLong": 0

Message History

Stores ids of components that were visited by the message in the message’s header.

[{name=sampleGateway, type=gateway, timestamp=1283281668091},
 {name=sampleChain, type=chain, timestamp=1283281668094}]

Message Store

Stores messages into configured persistent or in-memory storage including using JDBC and MongoDb.

Orderly Shutdown

Stop the application in an orderly manner. MBean exporter provides a JMX operation stopActiveComponents. Allows implementing custom shutdown behaviour of beans that implement OrderlyShutdownCapable.

Subscribe: Twitter , Facebook , RSS
Share on: Twitter , Facebook , Google+ , LinkedIn , Reddit .