Dynamic Microservice Topology Management for Latency and Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity and overhead associated with managing extensive networks of microservices, including increased communication latency, resource duplication, and security vulnerabilities, have led companies to reconsider microservices architecture in favor of monolithic structures.
Innovation Solution
A dynamic system that can adaptively switch between microservices and monolithic deployments based on real-time system monitoring and quality of service requirements, using mechanisms to optimize communication and resource utilization, and employing machine learning to predict future system states.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If microservices architecture is used, then scalability and ease of maintenance are improved, but device complexity and communication overhead increase
Solution Approach 1:
The patent implements dynamic topology adjustment where the system automatically reconfigures microservice connections based on real-time operational conditions. The topology manager monitors metrics and dynamically modifies service graphs, enabling the system to adapt between distributed microservices mode and consolidated monolithic mode, thereby resolving the contradiction between maintenance ease and complexity
Solution Approach 2:
The patent merges multiple microservices into a unified monolithic structure when operational conditions require reduced complexity. The topology manager consolidates service graphs into a single deployable unit, combining the benefits of microservice maintainability with monolithic simplicity, thus resolving the contradiction between ease of maintenance and device complexity
2Adaptability or versatility
If microservices architecture is used, then scalability is improved, but communication latency increases
Solution Approach 1:
The system dynamically adjusts the service topology based on operational conditions, switching between distributed microservices architecture for scalability and consolidated monolithic architecture for low latency. The topology manager monitors performance metrics and reconfigures connections in real-time, enabling the system to optimize between scalability and communication speed
Solution Approach 2:
The patent changes architectural parameters dynamically by adjusting the degree of service distribution. When latency is critical, the system consolidates services into a monolithic parameter state; when scalability is needed, it distributes services across multiple nodes. This parameter change enables optimization between communication latency and scalability
3Adaptability or versatility
If extensive network of microservices is used, then functional flexibility is improved, but security vulnerabilities increase
Solution Approach 1:
The patent consolidates multiple microservices into a unified monolithic structure when security risk assessment indicates excessive vulnerabilities. The topology manager merges service graphs into a single secure deployment, reducing the attack surface while maintaining functional flexibility through configurable service boundaries, thus resolving the contradiction between functional flexibility and security
4Productivity
If microservices are deployed, then resource utilization can be optimized, but duplicated resources increase
Solution Approach 1:
The patent merges duplicate resource instances across microservices into shared resources. The topology manager identifies and consolidates redundant components, enabling resource sharing across the service graph while maintaining the flexibility of microservices architecture, thus resolving the contradiction between resource utilization and duplicated resources
Data Source
AI summary
An apparatus, method, and computer-readable medium for configuring of microservices in a networked system. The method comprising monitoring one or more metrics of the networked system, determining a topology of the networked system based on the one or more metrics, and configuring of the plurality of microservices based on the topology.


