Comment on page
Event Driven Consumer
Do not be confused by Event-Driven name. This does not means it handles only Events. The name comes Messaging Patterns and means that Consumer will be triggered by a any type of Message instead of trying to poll it by it's own. Synchronous Command, Event or even a Query Handlers are actually Event Driven Consumers.
Polling consumers let actively poll for Messages rather than process messages in an event-driven manner. The Polling Consumer is created, when Endpoint is connected to
Pollable Channel.Polling Consumer is running in separate process.
consumer abstraction(Polling/Event Driven), which is automatically created based on connected channel takes responsibility from the developer, to create and maintain consumers manually. This process becomes dynamic and automatic and with low cost create possibility to pretty easily move from asynchronous code to synchronous and vice versa. Testing asynchronous code can be really cumbersome, but thanks to the abstraction, we can replace asynchronous channel with synchronous in tests. Which will lead to situation where endpoint in tests will be directly called, because
Event Driven Consumerwill be created.
The main idea behind
Ecotoneis to handle integration logic. Developer should not need to bother with creating consumers, testing asynchronous code. The best code is the code, which is not aware of being asynchronous code.