A StreamBase application is a single, deployable customer solution that can accept one or more incoming streams of structured data for processing, analysis, disposition, and potentially for display on a running TIBCO LiveView server.
StreamBase applications are composed of one or more fragments, which are executable units of an application. Supported fragment types are:
-
EventFlow fragments
-
LiveView fragments
-
Java object fragments
You develop, test, and debug fragments in TIBCO StreamBase Studio™, a provided Eclipse-based development environment. All Studio projects use the Maven project format and build system.
Fragments are executed in the context of a JVM engine.
One or more engines are encapsulated into a StreamBase Runtime container called a node. A node's lifecycle consists of installing, then starting the node. On completion, nodes are stopped, then removed.
A cluster is a logical grouping of one or more nodes.
Nodes and clusters are managed in the context of the StreamBase Runtime fabric, which is the overall combination of currently running nodes and clusters. The StreamBase Runtime does not have an independent existence, but comes into being when the first node is installed in the current subnet.
Nodes can be deployed:
-
In the context of a StreamBase Runtime fabric that can contain only a single node or can contain many nodes and clusters in different geographic locations.
-
In the context of Docker containers. Nodes hosted in Docker can still be managed as a StreamBase Runtime fabric with StreamBase provided tools.
Clusters of nodes can be configured to run in highly available configurations, with redundant nodes running the same StreamBase application.