Cloud Emulator for SaaS Failover Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-tenant SaaS environments, customers lack control over failover activation and experience downtime during maintenance or failures, which is problematic for entities requiring ultra-high availability, especially those in critical services like emergency medical care.
Innovation Solution
A system and method that create a cloud emulator outside the multi-tenant SaaS environment by extracting metadata and data records to provide an ultra-high availability platform with failover and failback control, allowing entities to access and modify their data independently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If entities use third-party multi-tenant SaaS environments, then cost and infrastructure management are improved, but control over failover activation and data availability is lost
Solution Approach 1:
The patent introduces a cloud emulator as an intermediary layer between the entity and the SaaS provider's multi-tenant environment. This emulator runs locally on the entity's infrastructure and emulates the SaaS environment, allowing the entity to maintain control over failover activation and data access while still leveraging the SaaS platform for primary operations. The emulator acts as a mediator that enables autonomous failover control without requiring changes to the third-party SaaS infrastructure.
2Reliability
If SaaS providers implement redundancy and failover mechanisms, then system reliability is improved, but failover activation time increases to 12-48 hours
Solution Approach 1:
The cloud emulator is configured in advance to mirror the SaaS environment's data structure and functionality. Before any failure occurs, the emulator maintains a synchronized copy of the entity's data and operational parameters. When failover is needed, the switch to the pre-configured emulator occurs immediately, eliminating the 12-48 hour activation delay inherent in traditional SaaS failover mechanisms. This preliminary preparation enables near-instantaneous failover while maintaining system reliability.
3Reliability
If entities require ultra-high availability for critical services, then service continuity is improved, but dependency on third-party SaaS control worsens
Solution Approach 1:
The system segments data access control into two distinct layers: the primary SaaS environment for normal operations and the local cloud emulator for failover scenarios. This segmentation allows the entity to maintain full control over data access and operational decisions during critical failures while continuing to leverage the SaaS provider's infrastructure for routine operations. The separation enables ultra-high availability without complete dependency on third-party control mechanisms.
Data Source
AI summary
The present disclosure relates to a system, method, and computer program for providing an ultra-high availability cloud emulator of an entity's data in a multi-tenant SaaS environment that is not controlled by the entity. The system extracts metadata related to the entity's data and user interface in the multi-tenant SaaS environment. The metadata is used to identify and extract data records for an entity from the multi-tenant SaaS environment, as well as to ascertain functional aspects of the entity user interface in the multi-tenant SaaS environment. A cloud emulator of the entity's data records and user interface in the multi-tenant SaaS environment is created using the extracted data records and metadata, where the cloud emulator is outside the multi-tenant SaaS environment. The entity is able to access the cloud emulator at the entity's discretion as a failover for the entity's data records in the multi-tenant SaaS environment and to modify the entity's data records in the cloud emulator.