How fledge-iot/fledge works
Main Components
• Core Service: Represent the central management unit (“services/core” and “python/fledge/services/core”) that handles REST APIs, scheduling, configuration management, and orchestrates the other services.
• South Service: Represented by directories “services/south” and “python/fledge/services/south,” these services handle the ingestion of sensor data, interacting with South plugins.
• Storage Service: Found in “services/storage” and “python/fledge/services/storage,” this component buffers sensor data (using SQLite by default, with support for PostgreSQL as well) and stores configuration/metrics.
• Optional/Additional Services: Include visualization, notification, and control dispatcher services (not fully integrated in the core tree but mentioned in the README and sometimes in separate directories or optional modules).
Interactions and Integration Points
• Storage Service interacts with plugin components (both for buffering data and executing scheduled purges and backups); indicate data flow from both Core and South services to Storage.
• REST API Endpoint: Show an external REST API (exposed by the Core service) used by local analytical applications and remote management interfaces. This API lets administrators get status updates (status commands as per the README).
Architectural Patterns and Principles
• Plugin/Extensibility Model: Clearly represent the plugin pattern where common interfaces allow South, North, and storage plugins to be independently developed and integrated.
Relevant Technologies and Frameworks
• Underlying technologies include Linux services, GCC (C/C++), Python, and SQLite (with PostgreSQL support available as an option).
• External integration points such as connections to historians, cloud services, Enterprise systems that Fledge forwards data to.