In the realm of Coreflux, a Flux Asset can be best understood as a specialized service or container, designed to perform a specific function within the IoT data hub. These assets are modular, allowing users to tailor their Coreflux environment to their specific needs. Whether it's data aggregation, computation, or establishing communication between devices and systems, Flux Assets are the building blocks that power the Coreflux platform.
What Makes a Flux Asset?
A Flux Asset is akin to a microservice in a microservices architecture. Each asset:
- Is Singular in Purpose: It does one thing and does it well.
- Is Independently Deployable: It can be deployed, upgraded, scaled, and restarted independently of other assets.
- Is Stateless: It does not retain any internal state between runs. Any required state is stored externally.
- Communicates Over the Network: It interacts with other assets and systems over standard network protocols, often HTTP or MQTT.
This design ensures that the Coreflux platform remains flexible, scalable, and resilient.
Available Flux Assets
Coreflux offers a diverse range of Flux Assets, each catering to different functionalities and use cases:
Orchestrators manage and coordinate the execution of other assets or tasks, ensuring that they run in the correct order and handle failures gracefully.
- Docker Orchestrator: Oversees the deployment, scaling, and management of Docker containers.
Aggregators pull data from various sources, process it if necessary, and then store it in a unified format or location.
- NoSql: Gathers and consolidates your topics into the broker, providing an upgrade to the dataHub being able to store and query data inside the Mqtt Broker.
Connectors act as bridges, enabling communication between different systems, devices, or databases.