Additional Notes
Why does a ‘Publisher’ in Reactive Streams matter in this design?
Track: Java
Topic: Reactive Streams
Focus: Non-Blocking I/O (Event Loops)
Java: Non-Blocking I/O (Event Loops)
Answer
A Publisher emits data to a Subscriber. Frame the concept in practical terms so you can explain it during interview discussion.
In Reactive Streams, the Publisher is responsible for producing data and sending it to a Subscriber. It follows a specific protocol to ensure backpressure and flow control. For instance, in a stock trading application, a Publisher might continuously emit live price updates to a Subscriber that processes these updates for display to users.
In Reactive Streams, the Publisher is responsible for producing data and sending it to a Subscriber. It follows a specific protocol to ensure backpressure and flow control. For instance, in a stock trading application, a Publisher might continuously emit live price updates to a Subscriber that processes these updates for display to users.
Topics: Java Non-Blocking I/O (Event Loops) Reactive Streams