Tenant-Specific Disaster Recovery Through Service Mesh Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud-computing customers face challenges in disaster recovery due to the high cost of replicating data to multiple datacenters, regulatory restrictions, and hyperscaler strategies, necessitating a tenant-specific approach that allows freedom of choice in datacenter selection and configuration for disaster recovery.
Innovation Solution
A computer-implemented method using a Routing Configurator and Replication Configurator to set up a service mesh and replication agents between datacenters, configuring Virtual Services and Ingress Gateways to route requests and replicate data according to tenant-specific preferences, enabling flexible disaster recovery configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is replicated to multiple datacenters across different regions, then disaster recovery capability is improved, but cost increases prohibitively for heterogeneous customers
Solution Approach 1:
The patent implements tenant-specific disaster recovery configurations where each customer can select their own primary and secondary datacenter locations based on their specific needs, regulations, and cost constraints. This allows heterogeneous customers to have customized DR configurations rather than a one-size-fits-all approach, enabling cost-effective disaster recovery for each organization individually.
2Reliability
If data is replicated to multiple datacenters, then continuous access during disasters is improved, but device complexity increases due to routing and replication configuration
Solution Approach 1:
The system performs preliminary configuration of routing and replication settings before disasters occur. Tenant-specific preferences for primary and secondary datacenter locations are established in advance, and replication configurations are pre-configured based on customer selections. This eliminates the need for complex real-time decision-making during disaster events.
Solution Approach 2:
The patent introduces an intermediary layer that manages the complexity of routing and replication configurations. This intermediary handles the coordination between multiple datacenters, service mesh configurations, and replication agents, shielding customers from the underlying complexity while enabling continuous access during disasters.
3Adaptability or versatility
If tenant-specific disaster recovery is implemented, then adaptability to customer preferences is improved, but system complexity increases due to per-tenant configuration management
Solution Approach 1:
The patent segments the disaster recovery system into tenant-specific configurations, where each customer has their own independently configured primary and secondary datacenter selections. This segmentation allows the system to accommodate diverse customer preferences and regulatory requirements while managing complexity through modular, isolated configuration management for each tenant.
Data Source
AI summary
A computer-implemented method includes translating into a routing configuration, tenant-specific preferences for primary and secondary datacenter locations. A service mesh is set up for communication between services within and across the primary and secondary datacenter locations. Service persistencies with endpoints in datacenter locations are used to configure replication agents between the service persistencies. Using service endpoints, configuring Virtual Services that implement the service mesh. An Ingress Gateway is configured to route end user requests into the service mesh to a first service instance in the tenant-selected primary datacenter. According to the tenant-specific preferences, data replication is configured to copy data to redundant storage. Using endpoints of persistent storage replication agents for each service persistence in the tenant-selected primary datacenter, configuring persistent storage replication agents for each service persistence in the tenant-selected primary datacenter.