How alexdragnea/upb-disertatie works
• Microservices Group:
• iot-bridge-service: Handles device communication and Kafka message production.
• iot-core-service: Acts as the core IoT service managing measurements, caching, and inter-service communication.
• iot-discovery-service: Enables dynamic registration/discovery of services.
• iot-gateway-service: Manages network entry, authentication, and routing (including Netty configurations).
• iot-user-service: Manages user accounts, API keys, authentication, and authorization.
• Front-end:
• iot-dashboard: A React-based application serving as the user interface.
• Shared Components:
• iot-commons: Contains common libraries, constants, DTOs, and Avro schemas used across services.
• Additional utilities such as performance testing (iot-performance-testing) which simulates IoT data flows.
• External / Infrastructure Services:
• Databases: MongoDB (document-store) and InfluxDB (time-series).
• Message Broker: Kafka (for asynchronous inter-service messaging).
• Cache and Additional services: Redis.
• Monitoring & Visualization: Prometheus (using prometheus.yml), Grafana (with dashboard JSONs), and possibly custom alerting.
• Certificates: Managed under the cert folder for secure communications.
Relationships and Interactions
• Directional data flows:
• REST interactions from the iot-dashboard (frontend) to the backend microservices (through API gateways) for data visualization.
• Kafka as the central event bus where the iot-bridge-service produces messages and the iot-core-service (among others) may consume these messages.
• That the microservices share a common library (iot-commons) to ensure consistency.
• Infrastructure connections from services to databases (InfluxDB, MongoDB) and caching solutions (Redis).
Architectural Patterns / Design Principles
• Microservices Architecture: Each service is independently deployable (evidenced by separate Maven projects, Dockerfiles, and Kubernetes manifests).
• API Gateway/Discovery: The presence of iot-gateway-service and iot-discovery-service implies dynamic routing and service discovery.
• Event-Driven and Asynchronous Communication: The use of Kafka along with Avro messages shows an event-driven design.
• Containerization and Orchestration: Use of Docker-compose files and various k8s YAML files emphasizes container-based deployments.
• Observability and Monitoring: Separate directories with monitoring dashboards and configuration files for InfluxDB, Prometheus, and Grafana.