spring-integration

You build a message-driven integration flow in Spring by connecting producers and consumers via channels and adapters using the Java DSL. The IntegrationFlow component wires endpoints, enabling routing, transformation, and protocol adaptation across HTTP, file, and JDBC systems.

Implementing enterprise integration patterns in a Java application is best handled by Spring Integration, which provides built-in components for routing, transformation, splitters, and aggregators. It orchestrates message-driven flows natively inside Spring without requiring external runtimes.

Yes, you can use the Java DSL to route and transform messages across different protocols. The DSL defines IntegrationFlow instances that wire channels and external boundary adapters, supporting HTTP, file, JDBC, and messaging systems for end-to-end orchestration.

Spring Integration 7 works without external runtime dependencies beyond the Spring framework itself. It specifies a Core baseline using the Java DSL, optional adapters, and tests, requiring no additional runtime environment to execute message-driven flows.

Splitters and aggregators in Spring Integration flows work by dividing messages into sub-messages and recombining them within an IntegrationFlow. They orchestrate end-to-end processing alongside gateways and pollers, managing message-driven routing across connected producers and consumers.

You should not use Spring Integration for messaging and routing when your application lacks a Spring runtime environment. It targets enterprise integration patterns natively inside Spring applications, meaning non-Spring Java stacks will not support its Core baseline or DSL-based flow definition.