The diagram below shows the key elements in SQLstream s-Server's system architecture, providing an overview of a SQLstream s-Server-based system in the context of external applications, data sources and sinks, databases, and other systems.
Streaming Data Protocol (SDP) is a protocol for efficiently transmitting rows between nodes in an instance of a SQLstream s-Server. SDP is also used for transmission of data between client and server, for example as part of INSERT EXPEDITED.
The SQLstream runtime component that manages and executes SQLstream s-Server applications.
SQLstream s-Server System Architecture
The blue-gray items are SQLstream s-Server components. The other items are the data and systems with which SQLstream s-Server interacts. External systems can be applications providing data as sources, receiving data as sinks, or supplying other forms of guidance, context, or control.
The control node is the 'brain' of a SQLstream network; it manages communication and optimization of messages and processing among SQLstream s-Server nodes. Every SQLstream system has a exactly one Control Node and at least one RAMP. The Control Node contains the repository, manages the list of sessions, and prepares statements later farmed out to nodes in the network.
Adapters are plug-ins that enable SQLstream s-Server to interact with an external system.
A SQLstream s-Server catalog is the highest level Repository Object; it contains Metadata and state information for the Catalog Objects (including streams, pumps and adapters) that comprise a SQLstream s-Server Repository.
JDBC stands for Java DataBase Connectivity, a standard Java API for connecting to relational databases and other data sources that can produce relational data.
These external interfaces are addressed through the SQL/MED facilities.
SQL/MED is an abbreviation for SQL Management of External Data. It is an API for making external data (both relational and non-relational) accessible within an SQL system.