Reflect review comments
This commit is contained in:
parent
984c081757
commit
cbc0ee484f
3 changed files with 3 additions and 4 deletions
|
|
@ -205,7 +205,7 @@ Distributed Data is intended to solve the following challenges:
|
||||||
Actors are a fundamental model for concurrency, but there are common patterns where their use requires the user
|
Actors are a fundamental model for concurrency, but there are common patterns where their use requires the user
|
||||||
to implement the same pattern over and over. Very common is the scenario where a chain, or graph, of actors, need to
|
to implement the same pattern over and over. Very common is the scenario where a chain, or graph, of actors, need to
|
||||||
process a potentially large, or infinite, stream of sequential events and properly coordinate resource usage so that
|
process a potentially large, or infinite, stream of sequential events and properly coordinate resource usage so that
|
||||||
faster operators do not overwhelm slower ones in the chain or graph. Streams provide a higher-level
|
faster processing stages do not overwhelm slower ones in the chain or graph. Streams provide a higher-level
|
||||||
abstraction on top of actors that simplifies writing such processing networks, handling all the fine details in the
|
abstraction on top of actors that simplifies writing such processing networks, handling all the fine details in the
|
||||||
background and providing a safe, typed, composable programming model. Streams is also an implementation
|
background and providing a safe, typed, composable programming model. Streams is also an implementation
|
||||||
of the [Reactive Streams standard](http://www.reactive-streams.org) which enables integration with all third
|
of the [Reactive Streams standard](http://www.reactive-streams.org) which enables integration with all third
|
||||||
|
|
|
||||||
|
|
@ -183,8 +183,7 @@ An example of how this API simplifies a stage can be found below in the second v
|
||||||
|
|
||||||
### Custom linear operators using GraphStage
|
### Custom linear operators using GraphStage
|
||||||
|
|
||||||
GraphStage allows for custom linear processing stages through letting them
|
To define custom linear operators, you should extend `GraphStage` using `FlowShape` which has one input and one output.
|
||||||
have one input and one output and using `FlowShape` as their shape.
|
|
||||||
|
|
||||||
Such a stage can be illustrated as a box with two flows as it is
|
Such a stage can be illustrated as a box with two flows as it is
|
||||||
seen in the illustration below. Demand flowing upstream leading to elements
|
seen in the illustration below. Demand flowing upstream leading to elements
|
||||||
|
|
|
||||||
|
|
@ -47,7 +47,7 @@ is running.
|
||||||
|
|
||||||
Operator
|
Operator
|
||||||
: The common name for all building blocks that build up a Graph.
|
: The common name for all building blocks that build up a Graph.
|
||||||
Examples of operators are like `map()`, `filter()`, custom ones extending @ref[`GraphStage`s](stream-customize.md) and graph
|
Examples of operators are `map()`, `filter()`, custom ones extending @ref[`GraphStage`s](stream-customize.md) and graph
|
||||||
junctions like `Merge` or `Broadcast`. For the full list of built-in operators see the @ref:[operator index](operators/index.md)
|
junctions like `Merge` or `Broadcast`. For the full list of built-in operators see the @ref:[operator index](operators/index.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue