I remember we have discussed about the way to express pipeline while ago.
I was fan of a "DSL" compared to the one we have in Camel: instead of
using apply(), use a dedicated form (like .map(), .reduce(), etc, AFAIR,
it's the approach in flume).
However, we agreed that apply() syntax gives a more flexible approach.
Using Java Stream is interesting but I'm afraid we would have the same
issue as the one we identified discussing "fluent Java SDK". However, we
can have a Stream API DSL on top of the SDK IMHO.
On 11/03/2018 19:46, Romain Manni-Bucau wrote:
don't know if you already experienced using java Stream API as a
replacement for pipeline API but did some tests:
It is far to be complete but already shows where it fails (beam doesn't
have a way to reduce in the caller machine for instance, coder handling
is not that trivial, lambda are not working well with default Stream API
However it is interesting to see that having such an API is pretty
natural compare to the pipeline API
so wonder if beam should work on its own Stream API (with surely another
name for obvious reasons ;)).
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github
<https://github.com/rmannibucau> | LinkedIn
<https://www.linkedin.com/in/rmannibucau> | Book