paoloambrosio
commented
2 years ago Framework Analysis
Resources:
- From Reactive Extensions to Reactive Streams - Bartosz Sypytkowski
Reactive Streams
| Dataflow | Reactive Streams |
|---|---|
SourceBlock<TOutput> |
IPublisher<T> |
TargetBlock<TInput> |
ISubscriber<T> |
IPropagatorBlock<TInput,TOutput> |
IProcessor<T, U> |
- Push/pull
- Don't seem to have picked up in .NET 🤦🏻♂️
Reactive Extensions
| Dataflow | Rx |
|---|---|
SourceBlock<TOutput> |
IObservable<T> |
TargetBlock<TInput> |
IObserver<T> |
IPropagatorBlock<TInput,TOutput> |
ISubject<TSource, TResult> |
DataflowBlockOptions.TaskScheduler |
.ObserveOn(_: IScheduler) |
- Push-based (OK for client applications)
- It is definitely a more modern pattern that extension developers would be more familiar with.
- Documentation is outdated (MSDN and Introduction to Rx) or non-existent (ReactiveX website). It still seems to be vary much alive (code and .Net YouTube channel).
- Books are available but outdated
- Rx.NET in Action (Manning 2017), T. Dresher - browsable for free 5m/day, new edition in MEAP.
- Reactive Programming for .NET Developers (Packt 2016), A. Esposito and M. Ciceri.
- Rx.Book (2019 draft), E. Petro.
- Functional Programming in C# (Manning 2017), E. Buonanno - has a chapter on "Data streams and the Reactive Extensions", second edition in MEAP due in 2021.
- Reactive.UI implements MVVM using Observables.
IAsyncEnumerable
- Pull-based
- No documentation... does it have any API to work with it?
Akka .NET
| Dataflow | Akka .NET |
|---|---|
SourceBlock<TOutput> |
Source<TOut, TMat> |
TargetBlock<TInput> |
Sink<TIn, TMat> |
IPropagatorBlock<TInput,TOutput> |
IFlow<TOut, out TMat> |
- Push/pull
- Less known in the community, and it not well integrated with the standard .NET libraries and frameworks
- Actors provide low-level interfaces to build anything we want with a simple concurrency model
- More powerful than we need
The Dataflow API has some major drawbacks:
Replace Dataflow with Rx.NET (see analysis below for why that was chosen).