General Concepts:
Components:
Features:
Configuration:
HowTo's:
—-
API's:
Client Applications:
Testing:
Functionality:
Component OverviewIn this document, we describe the software components of NebulaStream. The following figure illustrates its components: Controller LayerCommunication with NES happens either externally via Clients or internally via NesNodes. The external communication is managed by the Rest Server, which allows users to interact using a call to the Rest API (add link). The internal communication within NES is managed by the GRPC Server, which allows for the mutual request exchanges between the NES Workers and the NES Coordinator. Service LayerThe Service Layer provides functionality within NES. To this end, the Service Layer consists of a set of stateless-services, where each executes a particular request:
These services exploit the functionalities of lower services to fulfill their tasks and persist their information using components in the data access layer. Data Access LayerThe Data Access Layer is responsible for persisting the state of the system. The state consists of:
Management LayerThe Management Layer provides functionalities that are accessible by all components in the system:
|