Chapter 2: The Publisher and Subscriber APIs in a Reactor

1. How can we validate Reactive Streams publisher and subscriber implementations?

In order to validate a publisher, the Reactive Streams API has published a test compatibility kit called reactive-streams-tck. Reactive publisher can be verified using the PublisherVerifier interface. Similarly, a subscriber can be verified by using the SubscriberBlackboxVerification<T> abstract class.

2. How is the Reactive Streams publisher-subscriber model different from the JMS API?

In JMS, the producer is responsible for generating unbounded events on the queue or topics, while the consumer actively consumes the events. The producer and consumer are working in isolation, at their own rates. The task of managing the subscription is taken care of by the JMS broker. There is no concept of backpressure in JMS. Also, it lacks event modeling...