Containerized Microservice Deployment for Legacy Monoliths
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy monolithic applications are difficult to migrate and deploy as microservices due to their interdependent nature and compatibility issues with different instruction sets and APIs, making it challenging to execute them on modern computing environments.
Innovation Solution
A scalable container-based system that analyzes and partitions monolithic legacy applications into microservices by identifying transaction definition vectors, removing unused programs, and creating microservice images with complementary emulator elements, allowing deployment in a distinct computing environment with optimized resource allocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If monolithic legacy applications are migrated to modern computing environments, then compatibility with modern instruction sets and APIs is improved, but the interdependent nature of the software programs makes translation or migration very difficult
Solution Approach 1:
The patent applies segmentation by dividing the monolithic legacy application into multiple independent microservices. Each microservice is encapsulated in a separate container with its own execution environment, allowing them to be migrated and deployed independently. This segmentation resolves the technical contradiction by enabling modern compatibility at the microservice level while avoiding the complexity of migrating the entire monolithic application at once.
Solution Approach 2:
The patent introduces an intermediary layer consisting of containerization technology and orchestration systems. This intermediary enables legacy applications to run on modern infrastructure by providing translation and adaptation mechanisms, thus improving compatibility without requiring direct migration of the entire application, thereby reducing migration complexity.
2Reliability
If virtual machines are used to run legacy applications, then isolation and resource allocation are improved, but the starting up and tearing down of virtual machines requires considerable overhead
Solution Approach 1:
The patent replaces heavy-weight virtual machines with lightweight containers that can be created and destroyed rapidly. These containers share the host operating system kernel and do not require full guest operating systems, making them much faster to provision and tear down while maintaining adequate isolation through namespace and cgroup mechanisms.
Solution Approach 2:
The patent uses containerization technology that provides a thin abstraction layer over the host operating system. This flexible shell approach provides necessary isolation and resource management without the overhead of full virtualization, enabling rapid container lifecycle management while maintaining reliability.
3Loss of time
If containers are used instead of virtual machines, then starting up and tearing down requires little overhead, but containers share core operating system functions through kernel direct access which reduces isolation
Solution Approach 1:
The patent applies local quality by implementing fine-grained resource isolation within containers using Linux cgroups and namespaces. Each container is configured with specific resource limits and isolation boundaries tailored to its needs, providing appropriate isolation levels for critical functions while allowing shared kernel access for performance-critical operations.
Data Source
AI summary
The present disclosure provides a scalable container-based system implemented in computer instructions stored in a non-transitory medium. The present disclosure further provides a method of creating and operating a scalable container-based system.