Device Interaction
Data Orchestrator assumes devices are capable of exchanging data over a transport/protocol supporting SSL/TLS (e.g.: MQTT). This is a strong requirement, as Data Orchestrator identifies devices through client SSL certificates when it comes to data exchange.
Each transport implementation must be capable of mapping interfaces and out-of-band messages on top of it. Data Orchestrator itself does not care about the implementation detail of the transport itself, as the transport is in charge of converting its input to an AMQP message following Data Orchestrator's internal API specification.
Data Orchestrator's official reference and recommended design is MQTT using VerneMQ and its Data Orchestrator plugin.
Device SDK and Code Generation
Device SDKs can take advantage of the interface design to dynamically generate code for exchanging data with Data Orchestrator. This way, developers using Device SDKs are spared from knowing details about the underlying transports and protocols, and can use a data-driven API.
However, there are some limitations and requirements:
- The SDK requires SSL support - Data Orchestrator does not allow exchanging data over unencrypted channels and its design builds on the assumption that everything runs on top of SSL.
- As much as the SDK can implement virtually any transport protocol, it is required that the SDK supports at least HTTP(s) for Pairing.