Self-Assembling Microservices for OSS Infrastructure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In microservices-based OSS infrastructure, the complexity of managing numerous interrelated components leads to issues such as revisions getting out of sync, load balancing difficulties, and troubleshooting challenges, hindering migration and causing significant operational costs and productivity losses.
Innovation Solution
A system and method for self-assembling and self-configuring microservices, where a Host Resources Service Microservice (HRSMS) manages the startup and duplication of Directory Service Microservices (DSMS) and Tenant Microservices (TMS), ensuring the correct number of instances are running, and using APIs to monitor and configure services, with leader election processes for load balancing and resource management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If microservices are used to replace large OSS systems, then agility and flexible scaling are improved, but device complexity and difficulty of managing interconnections worsen
Solution Approach 1:
The patent implements self-healing mechanisms where the system automatically detects failures in microservices and restores them without human intervention. The system monitors service health, identifies failed components, and automatically reinstates them, allowing the complex microservice architecture to manage itself and reducing the burden on operators.
Solution Approach 2:
The patent employs continuous monitoring and feedback loops to track the state of microservices and their interconnections. This feedback mechanism enables the system to detect issues, analyze their impact, and trigger appropriate remediation actions, making the complex system more manageable through automated response to changing conditions.
2Adaptability or versatility
If the number of microservices increases, then functional versatility is improved, but troubleshooting difficulty and operational costs worsen
Solution Approach 1:
The patent implements comprehensive monitoring that tracks the state of each microservice and their interactions. This feedback system automatically detects failures, identifies their sources, and traces their impact through the system, making troubleshooting of complex multi-service architectures manageable through automated diagnostics.
Solution Approach 2:
The system automatically performs diagnostic and troubleshooting functions by monitoring service health, identifying failures, and restoring functionality without requiring manual intervention. This self-healing capability reduces operational costs and makes managing large numbers of microservices more efficient.
3Reliability
If manual integration testing is performed for each OSS module, then interface compatibility is ensured, but productivity and time-to-market worsen
Solution Approach 1:
The patent implements automated self-healing and self-configuration mechanisms that eliminate the need for manual integration testing. The system automatically verifies interface compatibility, detects conflicts, and resolves them through automated processes, maintaining reliability while dramatically improving productivity and reducing time-to-market.
Solution Approach 2:
The system employs continuous automated monitoring and testing that provides feedback on interface compatibility issues in real-time, allowing for immediate detection and resolution of problems without requiring lengthy manual testing cycles before deployment.
Data Source
AI summary
A system for managing systems with interrelated microservices with self-assembling and self-configuring microservices includes a plurality of host resource services microservices, a plurality of directory services microservices and a plurality of tenant microservices. Each of the microservices is provided with an API with a standard way to identify the API and its components, which together identify the functionality of the API in a common way. The host resources service microservice are started up in a host. A determination is made whether there is a directory service microservice running in the host and, if there is none, then spinning up a directory service microservice. A plurality of tenant microservices are installed and a determination is made whether all tenant microservices are running, If not, then copies of the tenant microservices that are not running are spun up.