This quickstart application demonstrates how to integrate Reactor into a Spring Integration application. It primarily focuses on TCP ingestion and publishing messages into a Channel after decoding in the Reactor ReactorTcpInboundChannelAdapter.
The classes are javadoc'ed and explain their purpose in the application. This app builds on several important Spring projects:
- Spring Boot powers the app and ties everything together in a simple and efficient way.
- Spring Integration provides the EIP abstractions for processing messages.
- Spring MVC provides a simple @RestController that provides some visibility into the running app.
- Reactor provides the horsepower to process over 1M msgs/sec via the Netty and RingBuffer-based TCP support.
To load test the application, simple send it length-field delimited data. The content of the messages in the default configuration is ignored since there's no message processing being done in this simple example. In your application, you'll want to add a real Codec and MessageHandler that do more than increment a counter.
There is a class in the tests called WriteLengthFieldDataFileApp which will write out a test file to src/main/resources/data.bin that is length-field-delimited random data. You can then use the veyr efficient LoadTestClient, also located in the test folder, to send that data to the server using the most efficient method possible. Benchmarking shows that using tools like netcat, or even a simple raw Socket-based app, will yield lower throughput than using the included FileChannel-based client. It's easy to get into a situation where you're actually load testing your load tester rather than the server-side components.
To run the Spring Integration components, fire up the app using the the QuickStartApplication class' Java main method, or by running it from the command line mvn spring:run.