Service Mesh Routing for Isolated Microservice Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing microservices environments face challenges in efficiently provisioning isolated environments for new changes without requiring a full copy of the original environment, which can be resource-intensive and introduce fragility due to broken flows, especially when multiple developers work on shared systems.
Innovation Solution
Deploy changed microservices alongside original instances within a service mesh, using smart routing based on deployment validator information from CI/CD processes to isolate environments, allowing developers to work independently without affecting others, and utilizing local resources for efficient development.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full copy of the original environment is created for each new change, then isolation for new changes is achieved, but resource consumption increases and fragility is introduced
Solution Approach 1:
The patent segments the microservices environment by introducing version tags and routing rules that divide traffic between original and new microservices. Instead of creating complete environment copies, the system segments the service mesh into isolated paths using metadata labels and routing policies, allowing independent validation of new changes while sharing common infrastructure resources.
Solution Approach 2:
The patent creates lightweight logical copies of the environment through service mesh routing configurations rather than physical environment copies. The routing rules and metadata tags act as virtual copies that redirect traffic to new microservice instances, providing environment isolation without duplicating underlying infrastructure resources.
2Reliability
If a full copy of the original environment is created for each new change, then isolation for new changes is achieved, but system fragility increases due to broken flows
Solution Approach 1:
The service mesh infrastructure serves multiple functions simultaneously: it routes traffic to both original and new microservices, maintains version control through metadata tags, enforces isolation policies, and provides observability. This universal infrastructure reduces system fragility by eliminating the need for separate, independently managed environment copies that could introduce broken flows.
Solution Approach 2:
The service mesh acts as an intermediary layer between clients and microservices, mediating all traffic flow through centralized routing rules. This intermediary manages the complexity of environment isolation by handling routing decisions, version management, and traffic splitting, preventing direct coupling between new and original microservices that could cause fragility.
3Productivity
If multiple developers work on shared microservices systems, then resource utilization is efficient, but environment isolation is reduced
Solution Approach 1:
The patent applies local quality by assigning unique metadata tags and routing rules to each developer's microservice instances. While the underlying infrastructure is shared, each developer's traffic flow is locally isolated through customized routing policies that identify and route to their specific microservice versions, providing environment isolation at the traffic flow level while maintaining resource sharing.
Solution Approach 2:
The system uses parameter changes in the form of metadata tags, version identifiers, and routing rule configurations to differentiate between multiple developers' environments. By dynamically changing these parameters based on deployment information from CI/CD processes, the system maintains environment isolation without requiring separate physical resources for each developer.
Data Source
AI summary
A system can maintain a microservices architecture on the system, wherein the microservices architecture comprises a group of microservices. The system can maintain a secure connection with a remote computer that is external to the system, wherein the remote computer executes a remote microservice. The system can receive a request to invoke the group of microservices. The system can invoke the remote microservice via the secure connection based on identifying the remote microservice using a tag of the request, wherein the tag is applied to the request by the system. The system can, after determining that the remote microservice has responded to the request, finish processing the request using the group of microservices.