How nhattannn222/customdevicehive works
Project Overview & Main Components
• This is a full-stack, containerized IoT management platform built on the open-source DeviceHive solution. It integrates additional functionality such as data storage and dashboarding (tracking temperature and humidity from an ESP8266 reading from a DHT11 sensor).
• The main components include:
• DeviceHive Containers: These include separate containers for DeviceHive’s backend, frontend, and authentication services (as referenced in the README log outputs – e.g. dh_backend, dh_frontend, dh_auth).
• Node.js Application: Found in the node_app directory; it likely handles custom business logic, REST API endpoints, or acts as a middleware component.
• ESP8266 Firmware: Located under the ESP8266_FIRMWARE folder, this is the Arduino sketch that runs on the IoT hardware, interfacing with the DHT11 sensor.
• Monitoring & Metrics: The lib/monitoring directory houses configuration files for Grafana dashboards, Prometheus, and possibly integrations with Kafka and a JMX Prometheus Java agent.
• Reverse Proxy / Messaging: The presence of nginx and MQTT broker configuration files implies components that manage routing and/or real-time messaging between devices and the platform.
• Auxiliary Docker & Environment Files: docker-compose.yml anchors the service orchestration.
Highlighting Architectural Patterns & Design Principles
• A containerized microservices architecture orchestrated via Docker Compose.
• Clearly separate concerns: device firmware at the edge (ESP8266), middleware (Node.js app), and backend services (DeviceHive-based containers).
• Integration points with external services (e.g., MQTT broker via Nginx configuration and the monitoring stack).