LwM2M (Light Weight Machine to Machine) architecture vs Web socket + HTTP architecture
Hello everyone,
I am aiming to build a desktop application for configuring and monitoring IoT devices (e.g., routers, switches, ciphers, sensors, etc.). To achieve this, I am considering two architectural approaches:
First Architecture:
The desktop application acts as a centralized LwM2M server (using Eclipse Leshan) to manage and configure IoT devices.
The IoT devices run Zephyr OS and act as LwM2M clients.
Second Architecture:
A backend-frontend architecture where:
Backend-Frontend Communication: Uses WebSocket for real-time updates.
Backend-Device Communication: Uses HTTP for scalability.
The biggest advantage is that the backend can handle many requests from IoT devices without failing, ensuring scalability.
I believe the second architecture is simpler and faster to implement compared to the first one. However, I need advice on the following:
How to use the registry in LwM2M and how to map it to a database for simplified management.
General advice on choosing the right architecture and simplifying the implementation.