One of the most frequently asked questions I get is: How can people learn about Streams? In the last couple of years, we have spent quite a bit of effort in the development of tutorials and getting started guides for Streams. The problem seems to be that people have a really hard time finding these documentation. To help users find our tutorials, we have created a new Streams Tutorials Hub on Github.
This Meetup will provide an overview and comparison of many different contenders in the fast growing streaming analytics space, then show a demo of IBM Streams technology allowing programs written completely in Python to call Streams libraries, and then deploy those apps to the Streams runtime.
Saving the planet one smart sprinkler at a time! This starter kit demonstrates the implementation of a smarter and connected water irrigation system. It is a great example of the reference architecture for Apache Quarks, and shows how it can be used in conjunction with Streaming Analytics Service on Bluemix.
I am very excited that the Quarks team will host our first ever Google+ Hangout event today. You can find details of this event here. Come join us live at 10 am PST, so you can ask the experts your questions. In case you cannot join us today, this event is recorded and you can always watch it later.
This event has inspired us to write more tutorials to help people get started with Apache Quarks (incubating) quickly.
When working on a Streams application, you often add Custom operators and trace statements in your applications to debug and understand what is happening. This is done by adding println statements in the logic clause of the Custom operator. To get the most up-to-date application output, you normally repeatedly gather the console logs for the PE in Streams Studio or Streams Console. This process can be quite cumbersome. Wouldn’t it be nice if you can automatically see the most updated console output in a terminal, without you having to collect the logs? We are going to show how you can do this.