Use cases
Possible uses of the BeeOS ecosystem
Last updated
Possible uses of the BeeOS ecosystem
Last updated
The gateway functionality will allow for the sending of telemetry or information to be collected to an external server in the cloud or on-premises, as well as the reception of information in the form of data, configurations, or commands.
At the edge, the gateway can send data to remote services and receive commands, data, or even configurations to be applied locally. A local hive can be configured at the edge to interconnect bees that collect information or even perform some type of process on a local machine or service. This hive can be connected to a parent hive in the cloud to collect information. Standalone bees (without a local hive) can also be installed to be connected directly to a hive in a remote location.
BeeOS offers the functionality of integrating an application with different services that use various protocols, without the need to develop connectivity with these services. This allows for the possibility of expanding to other types of protocols or services without having to modify the way the application communicates with them.
In a microservices-based architecture, services must communicate with each other using a messaging system or using a mechanism for service discovery to know the addresses where the different available services are located. Using a hive and HTTP bees in proxy mode located as container sidecars in Kubernetes pods, communication between microservices can be established based on the paths of the URLs or some header.
Using a hive as a service mesh adds the advantage of being able to interact with other services that are connected to some messaging system or other protocols (such as AMQP, Kafka or gRPC, etc).
The BeeOS ecosystem allows for the administration and monitoring of remote applications, following the entire provisioning lifecycle. This enables the deployment of any type of service anywhere, whether in the cloud, on-premise, or at the edge, without the need to physically move operators to the facilities where the services are installed or expose connections to the internet to allow accessing virtual machines from outside.
Additionally, it is possible to manage versioning for all installed components and monitor their health status in real-time. Centralizing logs and telemetry from remote installations is also possible, with integration with tools such as Prometheus. Remote applications can be installed as Docker containers or as pods in a container orchestrator such as Kubernetes.
By installing a hive server with a set of bees near a machine, data can be extracted and sent to the cloud, or it can be part of the process by performing computational tasks that expand the functionality provided by the machine. This can be achieved through workflows, scripting bees, and executing WASM code blocks.
Integration with artificial intelligence and machine learning systems for real-time data processing and analysis.
A hive server in the cloud can act as a gateway to receive data from remote bees or hives, possibly process that information and then store it in a data store or send it to an external service. It can also be used to send commands or data directly to bees on the edge (or bees connected to a hive on the edge). The hive in the cloud can receive data from other applications using the or through a bee connected to the hive with the appropriate protocol.
This can be achieved by using the provided by the hive server or by connecting to the bee messaging system using a bee of the desired protocol.
