How diogox451/datanumbers-iot works
Project type and purpose
• This is an IoT-platform composed of multiple microservices and a web client.
• Purpose: gather sensor data (via MQTT), centralize processing (via Pulsar queues), persist/analyze it (TimescaleDB/Postgres), manage devices, and provide a web interface.
File structure
• Top level:
• arduino/… → firmware for a temperature sensor.
• auth/… → Go-based authentication microservice (REST + JWT + Redis + Postgres).
• data-management-service/… → Spring Boot service for persisting and retrieving IoT data (Postgres, TimescaleDB, Pulsar).
• device_manager/… → Spring Boot microservice for device & template management (Postgres, Pulsar client).
• datanumbers-iot-web/… → Next.js/TypeScript web frontend.
• gateway-emqx/… → Go service that hooks into EMQX via gRPC for inbound MQTT messages, writes to Postgres and publishes to Pulsar.
• docker-compose.yaml → composition of all services and infrastructure (EMQX broker, Pulsar broker, Postgres, TimescaleDB, Redis, the microservices, and web UI).
Key insights from the README
• Gateways: EMQX for MQTT.
• Queue broker: Pulsar.
• Microservices: modular, distributed, written in Go and Spring Boot.
• Web UI in Next.js.
Detail without overthinking
• Break each microservice into two conceptual layers if desired: API/ingestion and persistence/service.
• Queues/topics and datastores.
• Avoid lumping everything together—show each microservice, its ingress/egress, and its data stores as separate components.