Hi guys, don't know if you already experienced using java Stream API as a replacement for pipeline API but did some tests: https://github.com/rmannibucau/jbeam
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 etc...). 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 ;)). Romain Manni-Bucau @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 <https://www.packtpub.com/application-development/java-ee-8-high-performance>
