Service interaction schema
WARNING
Arrows on the diagram indicate the direction of data flow.
| Letter | Meaning |
|---|---|
a | CRUD operations on the main Backend entities |
b | MQTT interaction: the Backend configures EMQX via REST, and subscribes to topics matching example.com/+/+/+/pepeunit |
c | CRUD operations on DataPipe data and Unit logs |
d | Read/Write operations: storing the token for EMQX issued by Backend and DataPipe, User verification in the Telegram Bot, Grafana authorization, state storage for the Telegram Bot, sending configuration change commands for DataPipe |
e | Read operations: authorizing Backend and DataPipe |
f | Multiple UPDATE operations for UnitNode states, UnitNode requests with DataPipe enabled |
g | MQTT interaction: DataPipe subscribes to topics matching example.com/+/pepeunit |
h | Multiple INSERT operations for UnitNode data and bulk DELETE for n_last_entry |
i | Read operations: reading configuration change commands from the Backend |
j | REST |
k | REST |
L | REST |
m | REST |
n | REST |
o | Any Programming Lang |
p | REST |
q | /var/run/docker.sock:ro + /var/lib/docker/containers:ro |
r | /var/run/docker.sock:ro |