Reactor Gateways

Search…
Reactor Gateways
The "Reactive Gateways" offer a reactive API wrapper around the command, query and event bus. Most of the operations are similar to those from non-reactive gateways, simply replacing the CompletableFuture with either a Mono or Flux. In some cases, the API is expended to ease use of common reactive patterns.
Reactor doesn't allow null values in streams. Any null value returned from the handler will be mapped to Mono#empty().
Retrying operations
All operations support Reactor's retry mechanism:
reactiveQueryGateway.query(query, ResponseType.class).retry(5);
This call will retry sending the query a maximum of five times when it fails.
Configuration in Spring Boot
This extension can be added as a Spring Boot starter dependency to your project using group id org.axonframework.extensions.reactor and artifact id axon-reactor-spring-boot-starter. The implementation of the extension can be found here.
Reactor Command Gateway
This section describes the methods on the ReactorCommandGateway.
send - Sends the given command once the caller subscribes to the command result. Returns immediately.
A common pattern is using the REST API to send a command. In this case it is recommend to for example use WebFlux, and return the command result Mono directly to the controller:
1
class SpringCommandController {
2
​
3
    private final ReactorCommandGateway reactiveCommandGateway; 
4
​
5
    @PostMapping
6
    public Mono<CommandHandlerResponseBody> sendCommand(@RequestBody CommandBody command) {
7
        return reactiveCommandGateway.send(command);
8
    }
9
}
Copied!
Sending a command from a Spring WebFlux Controller.
If the command handling function returns type void, Mono<CommandHandlerResponseBody> should be replaced with Mono<Void>
Another common pattern is "send and forget":
1
class CommandDispatcher {
2
​
3
    private final ReactorCommandGateway reactiveCommandGateway;
4
​
5
    public void sendAndForget(MyCommand command) {
6
         reactiveCommandGateway.send(command)
7
                               .subscribe();
8
    }
9
}
Copied!
Function that sends a command and returns immediately without waiting for the result.
sendAll - This method uses the given Publisher of commands to dispatch incoming commands.
This operation is available only in the Reactor extension. Use it to connect 3rd party streams that delivers commands.
1
class CommandPublisher {
2
​
3
    private final ReactorCommandGateway reactiveCommandGateway;
4
​
5
    @PostConstruct
6
    public void startReceivingCommands(Flux<CommandBody> inputStream) {
7
        reactiveCommandGateway.sendAll(inputStream)
8
                              .subscribe();
9
    }
10
}
Copied!
Connects an external input stream directly to the Reactor Command Gateway.
The sendAll operation will keep sending commands until the input stream is canceled.
send and sendAll do not offer any backpressure, yet. The only backpressure mechanism in place is that commands will be sent sequentially; thus once the result of a previous command arrives. The number of commands is prefetched from an incoming stream and stored in a buffer for sending (see Flux#concatMap). This slows down sending, but does not guarantee that the Subscriber will not be overwhelmed with commands if they are sent too fast.
Reactor Query Gateway
query - Sends the given query, expecting a response in the form of responseType from a single source.
1
class SpringQueryController {
2
​
3
    private final ReactorQueryGateway reactiveQueryGateway;
4
​
5
    // The query's Mono is returned to the Spring controller. Subscribe control is given to Spring Framework.
6
    @GetMapping
7
    public Mono<SomeResponseType> findAll(FindAllQuery query, Class<SomeResponseType> responseType) {
8
        return reactiveQueryGateway.query(query, responseType);
9
    }
10
}
Copied!
Recommended way of using the Reactor query gateway within a Spring REST controller.
scatterGather - Sends the given query, expecting a response in the form of responseType from several sources within a specified duration.
1
class SpringQueryController {
2
​
3
    private final ReactorQueryGateway reactiveQueryGateway;
4
​
5
    @GetMapping
6
    public Flux<SomeResponseType> findMany(FindManyQuery query) {
7
        return reactiveQueryGateway.scatterGather(query, SomeResponseType.class, Duration.ofSeconds(5)).take(3);
8
    }
9
}
Copied!
Sends a given query that stops after receiving three results, or after 5 seconds.
Subscription queries
Firstly, the Reactor API for subscription queries in Axon is not new.
However, we noticed several patterns which are often used, such as:
Concatenating initial results with query updates in a single stream, or
skipping the initial result all together.
As such, the Reactor Extension provides several methods to ease usage of these common patterns.
subscriptionQuery - Sends the given query, returns the initial result and keeps streaming incremental updates until a subscriber unsubscribes from the Flux.
Note that this method should be used when the response type of the initial result and incremental update match.
1
Flux<ResultType> resultFlux = reactiveQueryGateway.subscriptionQuery("criteriaQuery", ResultType.class);
Copied!
The above invocation through the ReactorQueryGateway is equivalent to:
1
class SubscriptionQuerySender {
2
​
3
    private final ReactorQueryGateway reactiveQueryGateway;
4
​
5
    public Flux<SomeResponseType> sendSubscriptionQuery(SomeQuery query, Class<SomeResponseType> responseType) {
6
        return reactiveQueryGateway.subscriptionQuery(query, responseType, responseType)
7
                                   .flatMapMany(result -> result.initialResult()
8
                                                                .concatWith(result.updates())
9
                                                                .doFinally(signal -> result.close()));
10
    }   
11
}
Copied!
subscriptionQueryMany - Sends the given query, returns the initial result and keeps streaming incremental updates until a subscriber unsubscribes from the Flux.
This operation should be used when the initial result contains multiple instances of the response type which needs to be flattened. Additionally, the response type of the initial response and incremental updates need to match.
1
Flux<ResultType> resultFlux = reactiveQueryGateway.subscriptionQueryMany("criteriaQuery", ResultType.class);
Copied!
The above invocation through the ReactorQueryGateway is equivalent to:
1
class SubscriptionQuerySender {
2
​
3
    private final ReactorQueryGateway reactiveQueryGateway;
4
​
5
    public Flux<SomeResponseType> sendSubscriptionQuery(SomeQuery query, Class<SomeResponseType> responseType) {
6
        return reactiveQueryGateway.subscriptionQuery(query,
7
                                                      ResponseTypes.multipleInstancesOf(responseType),
8
                                                      ResponseTypes.instanceOf(responseType))
9
                                   .flatMapMany(result -> result.initialResult()
10
                                                                .flatMapMany(Flux::fromIterable)
11
                                                                .concatWith(result.updates())
12
                                                                .doFinally(signal -> result.close()));
13
    }
14
}
Copied!
queryUpdates - Sends the given query and streams incremental updates until a subscriber unsubscribes from the Flux.
This method could be used when subscriber is only interested in updates.
1
Flux<ResultType> updatesOnly = reactiveQueryGateway.queryUpdates("criteriaQuery", ResultType.class);
Copied!
The above invocation through the ReactorQueryGateway is equivalent to:
1
class SubscriptionQuerySender {
2
​
3
    private final ReactorQueryGateway reactiveQueryGateway;
4
​
5
    public Flux<SomeResponseType> sendSubscriptionQuery(SomeQuery query, Class<SomeResponseType> responseType) {
6
        return reactiveQueryGateway.subscriptionQuery(query, ResponseTypes.instanceOf(Void.class), responseType)
7
                                   .flatMapMany(result -> result.updates()
8
                                                                .doFinally(signal -> result.close()));
9
    }
10
}
Copied!
In the above shown methods, the subscription query is closed automatically after a subscriber has unsubscribed from the Flux. When using the regular QueryGateway, the subscription query needs to be closed manually however.
Reactor Event Gateway
Reactive variation of the EventGateway. Provides support for reactive return types such as Flux.
publish - Publishes the given events once the caller subscribes to the resulting Flux.
This method returns events that were published. Note that the returned events may be different from those the user has published, granted an interceptor has been registered which modifies events.
1
class EventPublisher {
2
​
3
    private final ReactorEventGateway reactiveEventGateway;
4
​
5
    // Register a dispatch interceptor to modify the event messages
6
    public EventPublisher() {
7
        reactiveEventGateway.registerDispatchInterceptor(
8
            eventMono -> eventMono.map(event -> GenericEventMessage.asEventMessage("intercepted" + event.getPayload()))
9
        );
10
    }
11
​
12
    public void publishEvent() {
13
        Flux<Object> result = reactiveEventGateway.publish("event");
14
    }   
15
}
Copied!
Example of dispatcher modified events, returned to user as the result Flux.
Interceptors
Axon provides a notion of interceptors. The Reactor gateways allow for similar interceptor logic, namely the ReactorMessageDispatchInterceptor and ReactorResultHandlerInterceptor.
These interceptors allow us to centrally define rules and filters that will be applied to a message stream.
Interceptors will be applied in order they have been registered to the given component.
Reactor Dispatch Interceptors
The ReactorMessageDispatchInterceptor should be used to centrally apply rules and validations for outgoing messages. Note that a ReactorMessageDispatchInterceptor is an implementation of the default MessageDispatchInterceptor interface used throughout the framework. The implementation of this interface is described as follows:
1
@FunctionalInterface
2
public interface ReactorMessageDispatchInterceptor<M extends Message<?>> extends MessageDispatchInterceptor<M> {
3
​
4
    Mono<M> intercept(Mono<M> message);
5
​
6
    @Override
7
    default BiFunction<Integer, M, M> handle(List<? extends M> messages) {
8
        return (position, message) -> intercept(Mono.just(message)).block();
9
    }
10
}
Copied!
It thus defaults the MessageDispatchInterceptor#handle(List<? extends M> method to utilize the ReactorMessageDispatchInterceptor#intercept(Mono<M>) method. As such, a ReactorMessageDispatchInterceptor could thus be configured on a plain Axon gateway too. Here are a couple of examples how a message dispatch interceptor could be used:
1
class ReactorConfiguration {
2
​
3
    public void registerDispatchInterceptor(ReactorCommandGateway reactiveGateway) {
4
        reactiveGateway.registerDispatchInterceptor(
5
            msgMono -> msgMono.map(msg -> msg.andMetaData(Collections.singletonMap("key1", "value1")))
6
        );
7
    }
8
}
Copied!
Dispatch interceptor that adds key-value pairs to the message's MetaData.
1
class ReactorConfiguration {
2
​
3
    public void registerDispatchInterceptor(ReactorEventGateway reactiveGateway) {
4
        reactiveGateway.registerDispatchInterceptor(
5
            msgMono -> msgMono.filterWhen(v -> Mono.subscriberContext()
6
                              .filter(ctx-> ctx.hasKey("security"))
7
                              .map(ctx->ctx.get("security")))
8
        );
9
    }
10
}
Copied!
Dispatch interceptor that discards the message, based on a security flag in the Reactor Context.
Reactor Result Handler Interceptors
The ReactorResultHandlerInterceptor should be used to centrally apply rules and validations for incoming messages, a.k.a. results. The implementation of this interface is described as follows:
1
@FunctionalInterface
2
public interface ReactorResultHandlerInterceptor<M extends Message<?>, R extends ResultMessage<?>> {
3
​
4
    Flux<R> intercept(M message, Flux<R> results);
5
}
Copied!
The parameters are the message that has been sent, and a Flux of results from that message, which is going to be intercepted. The message parameter can be useful if you want to apply a given result rule only for specific messages. Here are a couple of examples how a message result interceptor could be used:
This type of interceptor is available only in the Reactor Extension.
1
class ReactorConfiguration {
2
​
3
    public void registerResultInterceptor(ReactorQueryGateway reactiveGateway) {
4
        reactiveGateway.registerResultHandlerInterceptor(
5
            (msg, results) -> results.filter(r -> !r.getPayload().equals("blockedPayload"))
6
        );
7
    }
8
}
Copied!
Result interceptor which discards all results that have a payload matching blockedPayload
1
class ReactorConfiguration {
2
​
3
    public void registerResultInterceptor(ReactorQueryGateway reactiveGateway) {
4
        reactiveQueryGateway.registerResultHandlerInterceptor(
5
            (query, results) -> results.flatMap(r -> {
6
                if (r.getPayload().equals("")) {
7
                    return Flux.<ResultMessage<?>>error(new RuntimeException("no empty strings allowed"));
8
                } else {
9
                    return Flux.just(r);
10
                }
11
            })
12
        );
13
    }
14
}
Copied!
Result interceptor which validates that the query result does not contain an empty String.
1
class ReactorConfiguration {
2
​
3
    public void registerResultInterceptor(ReactorQueryGateway reactiveGateway) {
4
        reactiveQueryGateway.registerResultHandlerInterceptor(
5
            (q, results) -> results.filter(it -> !((boolean) q.getQueryName().equals("myBlockedQuery")))
6
        );
7
    }
8
}
Copied!
Result interceptor which discards all results where the queryName matches myBlockedQuery.
1
class ReactorConfiguration {
2
​
3
    public void registerResultInterceptor(ReactorCommandGateway reactiveGateway) {
4
        reactiveGateway.registerResultHandlerInterceptor(
5
            (msg,results) -> results.timeout(Duration.ofSeconds(30))
6
        );
7
    }
8
}
Copied!
Result interceptor which limits the result waiting time to thirty seconds per message.
1
class ReactorConfiguration {
2
​
3
    public void registerResultInterceptor(ReactorCommandGateway reactiveGateway) {
4
        reactiveGateway.registerResultHandlerInterceptor(
5
            (msg,results) -> results.log().take(5)
6
        );
7
    }
8
}
Copied!
Result interceptor which limits the number of results to five entries, and logs all results.
Extensions - Previous
Reactor
Next - Extensions
Spring Cloud
Last modified 6mo ago
Copy link
Contents
Configuration in Spring Boot
Reactor Command Gateway
Reactor Query Gateway
Subscription queries
Reactor Event Gateway
Interceptors
Reactor Dispatch Interceptors
Reactor Result Handler Interceptors