Roles of Major Components
Various components take on their respective functions on the canvas within the project and work together to build applications that adhere to flexible and advanced business flows. By understanding the details of the components outlined below, you can make the most of exaBase Studio and build effective solutions to achieve your business objectives.
Description of Major Components
Each node is constructed on the circuit when the Blueprint is deployed and operates as an independent small service (Kubernetes Pod). For very simple applications, a single endpoint, entity, and SideApp can be sufficient.
| Name | Function | Use Case |
|---|---|---|
 Trigger | Receives events from multiple independent sources and retains state for pattern extraction including time | Continuously monitors one or more entities and kicks off the Pipeline only when conditions described in reactive language are met. By combining entity variables with Trigger descriptions, complex real-world events can be represented. |
 Entity | Holds references to data or files | Variables that store values or files. Supports input and output via endpoints, retaining reference information to data passed into and out of the Circuit, allowing definition of events for Function inputs and Trigger monitoring. |
 Endpoint | Web interface bound to an Entity | Enables retrieval and assignment of an entity's contents from external sources. |
 Pipeline | Listener for pipeline execution | Contains one or more Functions and can execute them sequentially. |
 Function | Holds the execution state of functions | Functions that operate within a Pipeline. Processing is containerized and uploaded to an external repository, with the URI noted in the Blueprint. Each function cold starts after the previous process finishes, allowing resource optimization. |
 SideApp | Runtime for custom containers | Can function as a web server that operates continuously for processing Pipeline when specific conditions are met. It can access resources on the Circuit. |