StreamBase Workshop, London 12/02/2007 – 14/02/2007

Pushing the project “Next Generation easyCredit” by getting used to the CEP platform “StreamBase” (www.streambase.com) was the reason for attending the workshop in London.

StreamBase staff course developer Dr. John Lifter was the leader of the workshop.

The team from the University of Applied Sciences of Regensburg/Germany

StreamBase has developed a high-performance CEP-platform that radically improves real-time data processing for multiple applications. The development of a StreamBase application can be set up in two different ways. An application can be created via either the GUI based approach on application diagrams or by writing the StreamSQL code.

GUI based approach
The development of StreamBase applications is done using an Eclipse-based IDE. Application diagrams are built using StreamBase Studio's graphical tools: visual components represent application components and streams of data. Application diagrams are stored in xml files with a .sbapp extension.
Most applications in production were designed via GUI. This approach is about dragging and dropping the required components, like prewritten operators, onto an application diagram editor and connecting them via arrows, the so called “arcs”. These arcs represent the flow of data throughout the application. Each component can be modified and configured individually. A component has at least one port by which they are affiliated with each other. Syntax checking or coding help is provided automatically by the studio.

The whole application based on the GUI-approach

StreamSQL Applications / Text-based approach
The StreamSQL is the text-based approach to describing StreamBase applications. StreamSQL applications are coded using a query language to describe the application and query streams of data. These StreamSQL applications are stored in text files with a .ssql extension. Many of the key words used in this approach are common to relational SQL (SELECT, WHERE, AS, ...) whereas some key words are stream-specific (CREATE STREAM, CREATE WINDOW,...). This way you can define an application as a collection of SQL-like statements. With StreamBase it is possible to combine those ways by for example by creating a module with either approach that can be used in applications designed with either approach.

Once you have written a StreamBase application, whether with the EventFlow graphical operators or in StreamSQL, your application is hosted by the StreamBase daemon. Independently of the application design, the daemon converts each EventFlow application or StreamBase document into a deployed application.

The result of the transfer via StreamBase daemon from the GUI-based SQL to StreamSQL

All applications which were designed in the application diagram via GUI approach on the first day were built by using the text-based complement. Pros of the coding compared to the GUI variant is the easy maintainability. You can e.g. search and replace names of variables in the code in the wink of an eye while you have to rename every single variable of the components in the application diagram manually.

In the end, both approaches StreamBase offers are equivalent. It depends on the developer which way he wants to design an application.

The event processing of the events generated by the easyCredit application can now be processed and correlated with StreamBase applications.


We thank our sponsors: TietoEnator, SimpleFact AG, and of course StreamBase Bill Hobib, Marc Simons and Ivan O'Sullivan for the invitation!


zuletzt geändert am: 13 Dec 2011 15:44

Aktuelle Schwerpunkte