+1 to exploring Reactive Streams
On Wed, Nov 23, 2016 at 12:25 PM, Timothy Spann
wrote:
> Reactive Streams is very cool, but only used by a few frameworks.
>
> https://en.wikipedia.org/wiki/Reactive_Streams
>
> Its adoption is slow, but starting to grow. I’ve worked
Apache family. Specifically to avoid issues like the json thing in the
other thread.
On Nov 23, 2016 12:40 PM, "Suneel Marthi" wrote:
> "keeping it in the family" - explain Family here?
>
> On Wed, Nov 23, 2016 at 1:29 PM, Trevor Grant
> wrote:
>
>
"keeping it in the family" - explain Family here?
On Wed, Nov 23, 2016 at 1:29 PM, Trevor Grant
wrote:
> Knowing nothing about Reactive streams, and already voicing my opinions
> about beam on this thread, I'd rather see Apache Beam be used if for no
> other reason
Knowing nothing about Reactive streams, and already voicing my opinions
about beam on this thread, I'd rather see Apache Beam be used if for no
other reason than "keeping it in the family", e.g. less worry about
managing dependency licenses, etc, etc.
Tg
Resident neigh-sayer of the thread
On Nov
Reactive Streams is very cool, but only used by a few frameworks.
https://en.wikipedia.org/wiki/Reactive_Streams
Its adoption is slow, but starting to grow. I’ve worked with RxJava and
Project Reactor. Once Spring 5 is out for a bit, then it will probably time
to look at the Reactive
On Mon, Nov 21, 2016 at 6:27 PM Joey Frazee wrote:
> I'm in favor of this for a few reasons:
>
> - There are enough stream processing frameworks out there that it makes it
> hard for us to offer much on that front. I don't think streams fills a gap
> for this internally
Opened:
STREAMS-460: Proof-of-concept: package and test streams processor with beam
APIs / local runner (https://issues.apache.org/jira/browse/STREAMS-460)
STREAMS-461: Proof-of-concept: package and test streams provider with beam APIs
/ local runner