kotlinx.coroutines-cn
Kotlin 协程的库支持 (by cnfn)
reactor-core
Non-Blocking Reactive Foundation for the JVM (by reactor)
| kotlinx.coroutines-cn | reactor-core | |
|---|---|---|
| 1 | 21 | |
| 1 | 4,824 | |
| - | 0.5% | |
| 0.0 | 9.4 | |
| over 5 years ago | 8 days ago | |
| Kotlin | Java | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
kotlinx.coroutines-cn
Posts with mentions or reviews of kotlinx.coroutines-cn.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-06-21.
-
Are there any good tutorials showing the use of Reactor streams using Kotlin?
Here is a general guide to reactive coroutines
reactor-core
Posts with mentions or reviews of reactor-core.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-10.
-
Is it wrong to use "try-catch" inside a reactive stream operator (project reactor)?
I was exploring reactive streams with project reactor and I encountered a use case where I needed to skip to the next event if an error occurred during the processing of the current event (e.g. deserialization issue).
-
Modern Async Primitives on iOS, Android, and the Web
Kotlin also has a construct for asynchronous collections/streams. Kotlin's version of AsyncSequence is called a Flow. Just as Swift's AsyncSequence builds upon prior experience with RxSwift and Combine, Kotlin's Flow APIs build upon earlier stream/collection APIs in the JVM ecosystem: Java's RxJava, Java8 Streams, Project Reactor, and Scala's Akka.
-
Alternatives to scala FP
Java's projectreactor.io ? It is widely used in Java world, see Spring WebFlux.
-
Hydroflow: Dataflow Runtime in Rust
I guess more a closer comparison would be with the Project Reactor https://projectreactor.io/ which is also a low level framework for data processing.
-
Reactive Backend Applications with Spring Boot, Kotlin and Coroutines (Part 1)
Spring Framework is one of the most popular choices for web applications. It comes with a great ecosystem, tooling, and support. Spring applications are mainly written in Java. While they can serve quite well in many different domains and use cases, they may not be a good fit for modern-day applications which require low-latency and high-throughput. This is where the reactive programming paradigm could help because the paradigm is designed to address these issues by its non-blocking nature. Spring already supports reactive programming via Project Reactor.
-
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.
- Angular for Junior Developers: Promises vs Observables
-
How much of real world programming involves using containers and for loops?
https://projectreactor.io/ https://docs.oracle.com/javase/8/docs/api/java/util/stream/Stream.html https://rxjs.dev/ https://developer.android.com/kotlin/coroutines https://developer.apple.com/documentation/combine
- Spring Reactor
-
Reactor bad, Loom good - but how will the landscape shape out?
With respect to Loom, it could be much easier for synchronous and reactive code to interoperate using schedulers that take advantage of Loom. The impact of Loom on Project Reactor was discussed in #3084, you might find it interesting.
What are some alternatives?
When comparing kotlinx.coroutines-cn and reactor-core you can also consider the following projects:
Reactive Streams - Reactive Streams Specification for the JVM
RxKotlin - RxJava bindings for Kotlin
RxJava - RxJava – Reactive Extensions for the JVM – a library for composing asynchronous and event-based programs using observable sequences for the Java VM.
reactor-kotlin-extensions
redux-kotlin - Predictable state container for Kotlin apps
Async Http Client - Asynchronous Http and WebSocket Client library for Java
Mutiny - An Intuitive Event-Driven Reactive Programming Library for Java
kotlin-monads - Monads for Kotlin
kotlin-result - A multiplatform Result monad for modelling success or failure operations.
Komprehensions - Do comprehensions for Kotlin and 3rd party libraries [STABLE]
result4k
kotlinx.coroutines-cn vs Reactive Streams
reactor-core vs Reactive Streams
reactor-core vs RxKotlin
reactor-core vs RxJava
reactor-core vs reactor-kotlin-extensions
reactor-core vs redux-kotlin
reactor-core vs Async Http Client
reactor-core vs Mutiny
reactor-core vs kotlin-monads
reactor-core vs kotlin-result
reactor-core vs Komprehensions
reactor-core vs result4k