Interacting with a Device
Devices interact with Data Orchestrator through their associated Transport. In this guide, we'll assume the Transport is MQTT/VerneMQ as per Data Orchestrator's defaults.
However, rather than implementing the whole Data Orchestrator protocol over MQTT, it is usually a better idea to rely on one of Data Orchestrator's SDKs.
Authentication/Pairing
Depending on how you plan on implementing Data Orchestrator's pairing mechanism, your devices might need an Agent for their first authentication or not. However, once they retrieve their Credentials Secret, they can implement Data Orchestrator's standard pairing routine to rotate their SSL certificate for accessing the transport.
In the most likely scenario in which you are using one of Data Orchestrator's SDKs, the SDK takes care of the whole pairing routine under the hood and, depending on your agent implementation, you just need to feed the SDK with either the Credentials Secret or the Agent Key.
Exchanging data
As per Data Orchestrator's protocol specification, data is exchanged based on the device's introspection. The device will be able to publish data on the transport on device interfaces, and receive data on server interfaces. In the MQTT case, the device will subscribe to its server interfaces' topics, and publish on its device interfaces topics.
Isolation and RBAC are guaranteed by the transport's ACL, which are usually orchestrated though a dedicated Data Orchestrator extension (as in the VerneMQ/MQTT case).
Again, Data Orchestrator's SDK allows you to interact with your device interfaces directly without caring about the underlying protocol and exchange details.