Reactive Streams · interview question

In the context of Reactive Streams, why is it important for a Publisher to adhere to the rule of signaling onComplete() or onError() only once?

Multiple choiceMediumchapter-19-curatedpremiumreactive-streamspublisher-and-subscriber

To ensure that multiple Subscribers can receive the same dataTo make sure the Subscriber has enough time to process each elementTo allow the Publisher to emit data infinitely without interruptionsTo ensure the Subscriber can manage its resources effectively

Answer and explanation

Correct answer

D. To ensure the Subscriber can manage its resources effectively

Why

The Reactive Streams specification requires a Publisher to signal onComplete() or onError() exactly once to ensure predictable and reliable behavior. If a Publisher signals completion or error multiple times, it can lead to resource mismanagement or inconsistent states in the Subscriber, violating the reactive contract.

Test yourself on Reactive Streams

A free test with instant, explained results. No account needed.

Start free test

All Reactive Streams questions →

In the context of Reactive Streams, why is it important for a Publisher to adhere to the rule of signaling onComplete() or onError() only once?

Correct answer

Why

More Reactive Streams questions