On Tue, Nov 7, 2017 at 4:20 PM, Eugene Kirpichov <[email protected]> wrote: > Wow, this is very exciting, thank you for the announcement!
It's great to see excitement! :-) > This obviously provokes curiosity, so a few questions: > - What are some features unique to this runner, i.e. features that might > make somebody who isn't using IBM Streams to consider using it just because > of how good is the Beam experience on it? I.e. things like - ease of use / > "no ops", performance, debugging/monitoring features, autotuning features, > etc. I think this is very much our 1.0 release of a IBM Streams runner with a focus on expanding our set of programming capabilities to include Beam pipelines. Thus the focus has been on seeing what Beam pipelines look like on IBM Streams and our cloud service (Streaming Analytics on IBM Cloud) as well as will Beam suit the types of applications our customers require. We envisage future work to further leverage features of our platform. For anyone interested in diving into Streams more here is the IBM link. https://www.ibm.com/cloud/streaming-analytics > - Is this runner a good fit for running large batch jobs, or is it focused > just on streaming use cases? Our focus has been streaming use cases. > - Have you tried validating the runner against the NexMark benchmark suite, > recently added to Beam? That's an excellent way to validate both correctness > and performance. I believe we are looking at that though I think it requires us to move to support 2.2. > - From a brief reading of the tutorial I didn't quite understand: is it > possible to play with this runner on a local machine? Ttwo answers: a) You can execute the runner locally to submit pipelines to a Streaming Analytics service or a distributed IBM Streams instance. b) You can execute pipelines as Streams applications in standalone mode (single process) but it requires a local Streams install, which are freely available for non-production use ("Quick Start Edition"). This is available as an install or a VM. > - For the support forum: why not StackOverflow? :) Or, do you plan to monitor > StackOverflow as well? I guess it fits in with our existing Streams community. If we saw questions on StackOverflow we would hopefully answer them. :-) Dan.
