Reactive Streams
Reactor
Reactive Streams | Reactor | |
---|---|---|
17 | - | |
4,814 | 332 | |
0.2% | - | |
1.9 | 0.0 | |
9 months ago | - | |
Java | Java | |
MIT No Attribution | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Reactive Streams
-
Reactive Programming with Spring Boot and Web Flux
Reactive Streams Specification
-
CompletableFuture vs Flow
Taken from https://www.reactive-streams.org/
-
Reactive Backend Applications with Spring Boot, Kotlin and Coroutines (Part 1)
Reactive programming is a paradigm that focuses on non-blocking and asynchronous processing of tasks. One set of specifications/abstractions for reactive programming on JVM is called Reactive Streams. Project Reactor is a message-driven, type-safe and functional implementation of Reactive Streams, and it is used by Spring (via spring-webflux module) to enable reactive web applications. Reactive streams model the data processing as a stream with one end producing the values and one end consuming them.
-
Brief Intro to Reactive Streams with Project Reactor
The reactive streams API provides the specification for non-blocking async streams processing with back pressure mechanism, and Project Reactor is an implementation written in java.
-
Whats the fuzz about Cats and Zio? ELI5
Cats Effect is a little more than just an IO effect implementation as they also provide an interface (or a standard) against implemented as typeclasses. You could think of it as a Java's Reactive Streams library which allows switching underlying implementation of actual effectful streaming.
-
Cosmos DB for Spring Developers, Part I: Using Cosmos DB as a SQL Database
NOTE: The Reactive Streams API and the implementation of it as provided by Spring WebFlux/Project Reactor is beyond the scope of this particular article. Please consult the appropriate documentation at the 'Web on Reactive Stack' Spring documentation site, any of several sessions I've delivered available on my YouTube channel, or by visiting the Reactive Streams and Project Reactor sites.
-
Show HN: Pidove, an Alternative to the Java Streams API
There is a very big design space for "Stream" APIs.
Microsoft's LINQ for instance can compile a stream operation into a SQL statement and JooQ does the same. That system offers query optimization and efficient joins that depend on the query system having complete visibility into the queries. indexes built ahead of time, etc.
Another extreme is a system like
https://www.reactive-streams.org/
that are especially good for apply a filter and map and other operations to a stream of real time events, e.g. instead of having a pull operation such as a for-loop over an Iterable, items go into the system from a stream.
I've worked on systems that use the later kind of streaming to run batch jobs and you can get great performance (780% speedup with 8 cpus) on crazy heterogenous workloads. You do have to be careful though to shut the system down or flush it out or otherwise you get wrong answers. Frequently those frameworks don't shut themselves down properly unless you implement clean shutdown yourself.
The point is that operators like "filter" and "map" and the rest are so powerful because they are portable between the minimal pidove up to a Hadoop cluster.
-
Quine Ingest Streams
Backpressure is a protocol defining how to send a logical signal UP the stream with information about the downstream consumers readiness to receive more data. That backpressure signal follows the same path as data moving downstream, but in reverse. If downstream is not ready to consume, then upstream does does not send.
-
What is the current state of the art for efficiently handling blocking requests in Java/Spring?
Reactive libraries like reactor are build on the Reactive Streams specification, just read that first sentence.
-
Project Loom: Understand the new Java concurrency model
Not a well written article. "Fiber" was dropped by spec team way back in favor of "virtual thread". Mentions "Rx Java" but not http://www.reactive-streams.org/ as a standard for existing async IO. I mean anyone who has done reactive java long enough can tell you about various implementations! I expected a better article from infoworld.com
Reactor
We haven't tracked posts mentioning Reactor yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
RxJava - RxJava – Reactive Extensions for the JVM – a library for composing asynchronous and event-based programs using observable sequences for the Java VM.
Mutiny - An Intuitive Event-Driven Reactive Programming Library for Java
reactor-core - Non-Blocking Reactive Foundation for the JVM
rsocket-java - Java implementation of RSocket
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
ea-async - EA Async implements async-await methods in the JVM.
kotlin-flow-extensions - Extensions to the Kotlin Flow library.
project-loom-c5m - Experiment to achieve 5 million persistent connections with Project Loom virtual threads