Service Mesh Assembly for Multi-Tenant Cloud Cost and Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud-computing applications face limitations in maximizing resource and operational cost savings due to the 'all-or-nothing' decision between multi-tenant and single-tenant service deployments, which does not accommodate user-specific requirements for scalability, security, high availability, disaster recovery, regulatory compliance, and customization needs.
Innovation Solution
A user demand-specific service mesh assembly approach that uses a mesh assembler to generate Assembly Profiles based on predefined templates and user-specific extensions, allowing for selective deployment of multi-tenant and single-tenant services, enabling customized service deployments and routing configurations to meet individual user needs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If all services are deployed in multi-tenant fashion to maximize cost sharing, then resource utilization and operational cost savings are improved, but strict isolation requirements for some tenants cannot be met
Solution Approach 1:
The patent segments the service deployment model into two distinct modes: multi-tenant and single-tenant. The system allows individual services to be independently configured in either mode, enabling tenants to share costs for non-critical services while maintaining strict isolation for critical services. This segmentation resolves the contradiction by allowing simultaneous multi-tenant and single-tenant deployments within the same system.
Solution Approach 2:
The patent introduces dynamic service mesh assembly that can adaptively configure deployment modes based on tenant requirements and service characteristics. The system dynamically determines which services should be multi-tenant and which should be single-tenant, allowing flexible transition between deployment strategies. This dynamic approach enables optimization of cost-sharing while meeting isolation requirements.
2Reliability
If single-tenant deployment is used to meet strict isolation requirements, then service isolation and security are improved, but resource sharing and cost savings are lost
Solution Approach 1:
The patent applies local quality by allowing different isolation levels for different services within the same tenant environment. Critical services receive single-tenant isolation while non-critical services use multi-tenant sharing. This localized application of isolation quality enables cost savings on non-critical services while maintaining security and isolation where required.
Solution Approach 2:
The patent changes the deployment parameter from a binary choice (all multi-tenant or all single-tenant) to a granular configuration where each service can independently select its deployment mode. This parameter change allows optimization of both cost and isolation by adjusting the deployment configuration of individual services based on their specific requirements.
3Ease of manufacture
If traditional all-or-nothing deployment decision is used, then deployment simplicity is maintained, but flexibility to optimize for different tenant needs is reduced
Solution Approach 1:
The patent creates a universal service mesh assembly framework that handles both multi-tenant and single-tenant deployments through a single system. The mesh assembler provides multi-functionality by supporting various deployment configurations, service types, and tenant requirements within one unified platform, eliminating the need for separate deployment systems.
Solution Approach 2:
The patent implements self-service through automated service mesh assembly that uses assembly profiles to automatically determine and configure appropriate deployment modes. The system autonomously analyzes service characteristics and tenant requirements to generate optimal deployment configurations without manual intervention, maintaining simplicity while enabling flexibility.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In an implementation, a mesh assembler receives a request for a new cloud-computing application tenant, where the request includes an assembly profile. The mesh assembler calls a deployment manager for applications and services that need to be custom deployed according to the assembly profile. The mesh assembler calls a routing configurator, which looks up services with certain attributes and configures services with certain attributes into a service mesh.