Skip to main content
Version: 0.12.0

Architecture FAQ

Design principles

The primary goal of is to simplify the connection of edge devices to the cloud by providing a secure and reliable cloud connectivity as well as a device management agent. The primary goal of is the ability to build IoT applications around a large diversity of components provided by independent actors.

For that purpose, focuses on:

  • Interoperability - lets the users integrate components producing or consuming telemetry data, northbound with cloud platforms, southbound with sensors as well as for east-west communication between analytics components.
  • Flexibility - lets users integrate component provided by different IoT actors, not even originally designed with in-mind, using various technologies and programming languages.
  • Security - provides a secure and stable foundation for cloud connections, software/firmware updates, and remote device management.
  • Reliability - components can survive in chaotic environments as network outages and process restarts happen.
  • Efficiency - lets users build applications that can run on constrained device hardware and with limited bandwidth networks.
  • Multi-cloud - enables users to connect their edge devices with multiple clouds. The actual cloud used can be decided at run-time by the end-user.

Why is an executable binary and not a library?

Interoperability of software components can be addressed along very different approaches. uses dynamic and loose inter-process communication (IPC) using messages exchange over an MQTT bus.

In the past and even today, many clouds provide a library (SDK) to help you connect your code to the cloud.

In we decided not to follow this approach because:

  • Libraries are programming language dependent, and thus developing a library for a number of programming languages always excludes developers using other programming languages. Additionally the effort to support many libraries (C, C++, Rust, Python, etc) is huge, including adding new features, testing, documentation, examples, Stack Overflow. Essentially we would create multiple small user groups instead of one large user group.
  • Using an IPC mechanism (and not a library) makes it easier to dynamically plug together components during runtime (instead of recompiling the software). For example, it is easier to add additional protocol stacks (OPC/UA, modbus, ProfiNet, IO-Link, KNX, ...) to during run-time.
  • Linking libraries to existing code can be problematic for some developers, for example for licensing reasons. While has a very user-friendly licensing (Apache 2.0), some developers prefer to reduce the number of libraries that they link to their software.

Why does use MQTT for IPC?

MQTT is a lightweight and flexible messaging protocol widely used by IoT applications.

We were looking for a widely-used, performant IPC mechanism and we investigated a number of alternatives. In the end, we decided to use MQTT for the following reasons:

  • The approach is used by other industrial IoT organisations and software, for example by Open Industry 4.0 Alliance.
  • Existing components (like Node-RED or collectd ) that support MQTT can be easily integrated. In this case, acts as an MQTT proxy: existing components connect to the local MQTT bus of, and routes the messages to different clouds in a secure and reliable manner.
  • MQTT is message oriented and bi-directional, which matches well with the event oriented programming model of industrial IoT.
  • MQTT is available on many platforms, including Linux and Windows.
  • MQTT client libraries are available for 25+ programming languages (see])
  • MQTT overhead is relatively small in terms of client library size and network overhead.
  • MQTT is message payload agnostic which enables sending not only JSON messages, but also text, CSV or binary data.

Alternatives considered where: DBus, gRPC and REST over HTTP.

Why does use MQTT for cloud communication?

MQTT is a lightweight and flexible messaging protocol widely used by IoT applications. Nearly all the IoT cloud platforms provide an MQTT endpoint to consume and publish messages from a fleet of devices. Therefore, MQTT was an obvious choice for edge to cloud communication.

Using MQTT for cloud communication is not mandatory. You are free to add additional protocols beside MQTT: Because has an internal bus, you can implement a bridge to another protocol (e.g. LWM2M or plain HTTPS). In that case, MQTT is used inside the edge devices, and another protocol is used for external communication.

Why is the canonical format based on JSON?

Thin-Edge-Json, the cloud-agnostic message format of, is based on JSON.

Supported by nearly all programming languages, JSON provides a nice compromise between simplicity and flexibility. Notably, it features duck typing, a flexible way to group different data fields that can be read by consumers with different expectations over the message content. For instance, a consumer expecting a temperature can process messages where the temperature measurements are produced along with other kinds of measurements.

Additionally, JSON is supported by most (if not all) cloud vendors, which makes the transformation easier.

JSON is also used by other (Industrial) IoT standards, including OPC/UA and LWM2M.

Why use Rust?

The command line interface, and the daemon processes of are implemented in Rust, a language empowering everyone to build reliable and efficient software.

The main motivation to use Rust is security: Rust avoids many security vulnerabilities and threading issues at compile time. With the type system of Rust you write software that is free from typical security flaws: undefined behavior, data races or any memory safety issues.

The second motivation is efficiency. Rust software is typically as efficient as C/C++ software. One reason is that Rust does not have (by default) a garbage collector. Instead, memory lifetime is calculated at compile time.

Note that, even if the core of is written in Rust, any programming language can be used to implement components. For that, one just needs an MQTT library that lets them interact with the MQTT broker.