Virtualized Containers for Legacy Application Multi-Tenant Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy applications designed for on-premise single-tenant environments cannot be directly executed in multi-tenant computing environments like cloud computing due to lack of support for full isolation, scalability, elasticity, fault-tolerance, high availability, and resource management.
Innovation Solution
Migrating legacy applications to a multi-tenant computing environment by instantiating virtualized computing containers, isolating instances securely, and modifying them to use databases for configuration and state management, and adding REST APIs and HTML interfaces for load balancing and dispatching requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If legacy applications are migrated to multi-tenant computing environment using virtualized containers, then isolation and security are improved, but device complexity increases
Solution Approach 1:
The system segments the legacy application into isolated virtualized containers, where each container represents a discrete execution environment with its own process space, file system, and network stack. This segmentation enables strong isolation between tenants while maintaining the legacy application's original codebase, resolving the contradiction by achieving security through structural division rather than complex access control mechanisms.
Solution Approach 2:
A container runtime intermediary layer is introduced between the legacy application and the host operating system. This intermediary handles system calls, resource management, and isolation enforcement, allowing the legacy application to run unchanged while the intermediary provides the security and isolation guarantees required in multi-tenant environments. The complexity is shifted from the application layer to the infrastructure layer.
2Reliability
If virtualized computing containers are used to isolate legacy application instances, then security and isolation are improved, but ease of operation deteriorates
Solution Approach 1:
The containerized legacy application instances are designed to self-manage their operational state, including automatic startup, configuration loading, and health monitoring. The container runtime automatically handles lifecycle management, reducing the operational burden on users while maintaining strong isolation boundaries.
3Adaptability or versatility
If legacy applications are executed in virtualized containers with database integration, then adaptability and scalability are improved, but device complexity increases
Solution Approach 1:
A universal database interface layer is implemented that works across all containerized legacy application instances regardless of their original data storage mechanisms. This interface layer provides standardized access patterns for configuration data and tenant-specific data, enabling multi-tenant scalability without requiring each legacy application to be individually adapted to complex data management systems.
4Productivity
If multiple tenant requests are load-balanced to legacy application instances, then productivity and resource utilization are improved, but device complexity increases
Solution Approach 1:
Multiple legacy application instances running in virtualized containers are merged into a unified service endpoint that accepts tenant requests. The container runtime and orchestration system automatically distribute requests across instances based on resource availability and tenant requirements, achieving high resource utilization without requiring complex external load balancing infrastructure.
Data Source
AI summary
Various embodiments migrate a legacy application to a multi-tenant computing environment. In one embodiment, at least one virtualized computing container is instantiated on a host system in a multi-tenant computing environment. An instance of the legacy application is executed within the virtualized computing container. The legacy application having been initially configured to run on premise and serve one tenant at a time. The virtualized computing container securely isolates the executing instance of the legacy application from other executing instances of the legacy application. At least one request received from a first client is sent to the instance of the legacy application executing within the virtualized computing container. The virtualized computing container is quiesced based on at least one quiescing criterion having been satisfied by the instance of the legacy application.