Distributed Telemetry Policy Gateway REST Framework
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Monolithic software systems face challenges in scalability and modularity as complexity increases, leading to productivity issues and increased coupling between modules, which hinders the ability to achieve high optimization and feature velocity.
Innovation Solution
A highly scalable RESTful framework is introduced, enabling a distributed Telemetry and Policy Gateway (TPG) for policy, configuration, and metric publication, along with an election mechanism for randomly selecting devices for metric measurement and geo-tagging of metrics, facilitating modular communication between software modules in monolithic systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If a monolithic software system is used, then hardware efficiency and latency are optimized, but scalability and modularity deteriorate as complexity increases
Solution Approach 1:
The system segments the monolithic architecture by introducing a RESTful framework that enables modular microservices while maintaining a core monolithic structure. This allows time-sensitive modules to remain integrated for low latency, while non-time-sensitive modules can be separated into independent services for better modularity and scalability.
Solution Approach 2:
Different parts of the system are given different architectural qualities: core data path modules maintain tight integration for hardware efficiency and low latency, while new requirements and rewrites are implemented as separate microservices for improved modularity and feature velocity.
2Adaptability or versatility
If microservices are used, then modularity and feature velocity are improved, but hardware efficiency and latency increase due to inter-module communication
Solution Approach 1:
The architecture segments services based on their latency requirements: time-sensitive operations remain in the monolithic core with direct hardware access, while non-time-sensitive operations are delegated to microservices, minimizing the impact of inter-service communication on overall system latency.
Solution Approach 2:
The system dynamically determines whether to process requests in the monolithic core or delegate to microservices based on time sensitivity requirements, allowing flexible optimization of latency for different operation types.
3Adaptability or versatility
If the system grows in complexity, then functionality increases, but coupling between modules increases and productivity decreases
Solution Approach 1:
The system segments functionality into independent microservices that can be developed, tested, and deployed separately. This reduces coupling between modules, allowing different teams to work on different services simultaneously without affecting each other, thereby maintaining high productivity as the system grows.
Solution Approach 2:
The RESTful framework provides universal communication protocols and patterns that work across all microservices, reducing the need for custom integration logic and enabling faster development of new features through standardized interfaces.
Data Source
AI summary
Systems and methods include connecting to and authenticating a plurality of user devices; utilizing a plurality of RESTful (Representational State Transfer web service) endpoints to communicate with the plurality of user devices; providing any of policy and configuration to the plurality of user devices utilizing version number via a RESTful endpoint; caching the any of policy and configuration for each device of the plurality of user devices; and receiving metrics based on measurements at the plurality of user devices according to corresponding policy and configuration, via a RESTful endpoint.