Unified Microservice Deployment With Spring Context Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing microservice deployments require significant hardware resources and result in high communication latency due to the need for multiple replicas and shared libraries, with system startup times and resource usage proportional to the number of deployments.
Innovation Solution
Unified deployment of microservices into a single deployment artifact, using a Spring context hierarchy to create isolated contexts for each microservice, enabling in-process communication and reducing the need for remote calls.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple microservices are deployed separately with multiple replicas, then high availability requirements are met, but hardware resources and system startup time increase proportionally
Solution Approach 1:
The patent merges multiple microservice deployments into a single unified deployment artifact that contains all microservices. This consolidation reduces the number of separate deployment units, thereby reducing hardware resources required while maintaining the ability to run multiple microservice instances for high availability through process-level replication rather than deployment-level replication.
Solution Approach 2:
The unified deployment artifact serves as a universal container that can host multiple microservices simultaneously. This multi-functional artifact replaces multiple specialized deployment units, reducing overall system resource consumption while maintaining the capability to support multiple services with their respective replicas.
2Adaptability or versatility
If multiple microservices are deployed separately, then independent deployment flexibility is maintained, but communication latency increases due to remote calls
Solution Approach 1:
By merging multiple microservices into a single deployment artifact, the patent enables them to run in the same process space, eliminating network communication overhead for inter-service calls. This results in significantly faster communication while maintaining independent deployment flexibility through the unified artifact approach.
3Adaptability or versatility
If separate deployment artifacts are used for each microservice, then independent CI/CD is enabled, but system complexity and deployment time increase
Solution Approach 1:
The patent combines multiple microservice deployment artifacts into a single unified artifact that can be deployed together. This reduces deployment complexity by eliminating the need to manage multiple separate deployment units, while independent CI/CD is maintained through modular architecture within the unified artifact.
4Reliability
If multiple replicas of each microservice are deployed, then high availability is achieved, but processing global changes requires restarting many deployments
Solution Approach 1:
By consolidating multiple microservices into a single deployment artifact, the patent reduces the number of deployment units that need to be restarted during global changes. Only the unified artifact needs to be restarted rather than multiple separate microservice deployments, significantly reducing the time loss associated with global changes while maintaining high availability through process-level replication.
Data Source
AI summary
As described herein, a system, method, and computer program are provided for unifying deployment of microservices. A plurality of microservices to be deployed to a system are determined. Deployments of the plurality of microservices are unified into a single deployment of the plurality of microservices to the system.