如何在准备就绪时使用反应式 Flux/Mono 将消息推送到上游而不是在间隔中轮询状态？

Question

Trying to push message to upstream whenever they are available/ready and close connection after flush, rather than polling for message using spring reactive flux interval.

@GetMapping(value = "/getValue/{randomId}", produces = MediaType.TEXT_EVENT_STREAM_VALUE)
public Flux<String> statusCheck(@PathVariable("randomId") @NonNull String randomId) {

return Flux.<String>interval(Duration.ofSeconds(3))
                .map(status -> {
                    if (getSomething(randomId).
                            equalsIgnoreCase("value"))
                        return "value";
                    return "ping";
                }).take(Duration.ofSeconds(60)).timeout(Duration.ofSeconds(60));
    }

Kafka listener updates randomId value in a map as it gets, getSomething method checks for randomId value in intervals in map. So instead of checking in intervals and storing data in map, i want to push message to client when listener receives.

Answer 1

This sounds like a Flux.create() request:

return Flux.<String>create(emitter -> {
     if (getSomething(randomId).equalsIgnoreCase("value")) {
          sink.next("value");
     }
     else {
          sink.next("ping");
     }
  });

---

/**
 * Programmatically create a {@link Flux} with the capability of emitting multiple
 * elements in a synchronous or asynchronous manner through the {@link FluxSink} API.
 * This includes emitting elements from multiple threads.
 * <p>
 * <img class="marble" src="doc-files/marbles/createForFlux.svg" alt="">
 * <p>
 * This Flux factory is useful if one wants to adapt some other multi-valued async API
 * and not worry about cancellation and backpressure (which is handled by buffering
 * all signals if the downstream can't keep up).
 * <p>
 * For example:
 *
 * <pre><code>
 * Flux.&lt;String&gt;create(emitter -&gt; {
 *
 *     ActionListener al = e -&gt; {
 *         emitter.next(textField.getText());
 *     };
 *     // without cleanup support:
 *
 *     button.addActionListener(al);
 *
 *     // with cleanup support:
 *
 *     button.addActionListener(al);
 *     emitter.onDispose(() -> {
 *         button.removeListener(al);
 *     });
 * });
 * </code></pre>
 *
 * @reactor.discard The {@link FluxSink} exposed by this operator buffers in case of
 * overflow. The buffer is discarded when the main sequence is cancelled.
 *
 * @param <T> The type of values in the sequence
 * @param emitter Consume the {@link FluxSink} provided per-subscriber by Reactor to generate signals.
 * @return a {@link Flux}
 * @see #push(Consumer)
 */
public static <T> Flux<T> create(Consumer<? super FluxSink<T>> emitter) {

Answer 2

I built solution based on this stackoverflow Spring 5 Web Reactive - Hot Publishing - How to use EmitterProcessor to bridge a MessageListener to an event stream answer, used EmitterProcessor to hot publish message as they are available.

Here is the sample code

@GetMapping(value = "/getValue/{randomId}", produces = MediaType.TEXT_EVENT_STREAM_VALUE)
public Flux<String> statusCheck(@PathVariable("randomId") @NonNull String randomId) {
    EmitterProcessor<String> emitterProcessor = EmitterProcessor.create();
    Flux<String> autoConnect = emitterProcessor.publish().autoConnect();
    FluxSink<String> sink = emitterProcessor.sink();
    //storing randomId and processor sink details
    randomIdMap.putIfAbsent(randomId, emitterProcessor);
    /** This will return ping status to notify client as 
    connection is alive until the randomId message received. **/
    sendPingStatus(sink, randomId);
}

Below method shows how to pushes message to client as it arrives on kafka consumer and close flux connection.

@KafkaListener(topics = "some-subscription-id",
        containerFactory = "kafkaListenerContainerFactory")
public void pushMessage(SomeMessage message, Acknowledgment acknowledgment) {
    EmitterProcessor emitter = randomIdMap.get("randomId");
    if (emitter != null ) {
        emitter.onNext(message);
        emitter.onComplete();
        randomIdMap.remove("randomId");
        acknowledgment.acknowledge();
    }
}