There are standards in many aspects of software development, and reactive programming has not escaped this. There is a Reactive Streams initiative to standardize asynchronous stream processing. The specific focus, in the context of Java, is with the JVM and JavaScript.
The Reactive Streams initiative aims at tackling the issue of governing how the data stream is exchanged between threads. As you will recall from the previous section, the idea of processors is predicated on there being no impact on the publisher or receiver. This no-impact mandate stipulates that the following are not required:
- Data buffering
- Data translation
- Conversion
The basic semantics of the standard define the regulation of data ...
