Microservice Lifecycle Containers for Tenant Artifact Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-tenant cloud service environments, updating tenant artifacts across different versions of cloud services is complex, leading to incompatibilities and potential outages due to the need for manual compatibility tracking and latency in artifact creation, which can result in service disruptions and violate zero-downtime SLAs.
Innovation Solution
A distributed approach using loosely-coupled microservice lifecycle containers, each managing its own requirements, with an infrastructure lifecycle service coordinating tenant artifact creation/update across multiple microservices, ensuring compatibility and minimizing downtime by front-loading updates and making them idempotent for resilience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual compatibility tracking is used for tenant artifacts across different cloud service versions, then compatibility between versions can be managed, but the process becomes complex and time-consuming
Solution Approach 1:
The system segments the artifact creation process into multiple independent microservice lifecycle containers, each responsible for specific artifact creation tasks. This segmentation eliminates the need for manual compatibility tracking by automating the process through coordinated microservices that independently manage their own artifact creation and versioning requirements.
Solution Approach 2:
The system performs preliminary actions by pre-defining artifact creation templates and compatibility rules in the microservice code repository. These templates are automatically applied during artifact creation, eliminating the need for manual compatibility tracking and reducing process complexity while ensuring version compatibility.
2Productivity
If tenant artifacts are created or updated in real-time, then service continuity is maintained, but latency occurs causing service disruptions
Solution Approach 1:
The system performs artifact creation and validation operations in advance during the microservice deployment phase, rather than in real-time during tenant operations. The infrastructure lifecycle service pre-creates artifact templates and validates compatibility before tenant instantiation, eliminating runtime latency while maintaining service continuity.
Solution Approach 2:
The system uses artifact templates and copies proven compatible configurations from the microservice code repository. Instead of creating artifacts from scratch in real-time, the infrastructure lifecycle service retrieves and adapts pre-validated templates, significantly reducing creation latency while ensuring compatibility.
3Adaptability or versatility
If multiple versions of cloud service are supported, then versatility is improved, but incompatibilities between different versions occur
Solution Approach 1:
The system applies local quality by allowing each microservice lifecycle container to have version-specific artifact creation logic and compatibility rules. Each microservice can define its own artifact templates and validation criteria tailored to its version requirements, while the infrastructure lifecycle service coordinates them to ensure overall system compatibility.
Solution Approach 2:
The system manages version compatibility by dynamically changing parameters such as artifact templates, configuration files, and validation rules based on the target cloud service version. The infrastructure lifecycle service automatically selects and applies the appropriate parameter set for each version, ensuring compatibility without sacrificing versatility.
4Stability of the object's composition
If centralized coordination of tenant artifacts is implemented, then consistency is improved, but system complexity increases
Solution Approach 1:
The system segments the coordination function into distributed microservice lifecycle containers that independently manage their own artifact creation. The infrastructure lifecycle service provides lightweight coordination by routing requests and harmonizing outputs, rather than implementing complex centralized control, thus maintaining consistency with reduced system complexity.
Solution Approach 2:
The infrastructure lifecycle service implements a universal coordination mechanism that handles multiple artifact types and microservice versions through a single standardized interface. This multi-functional approach ensures consistency across diverse artifacts without requiring separate complex coordination systems for each case.
Data Source
AI summary
In accordance with an embodiment, described herein is a system and method for use with a cloud computing environment, for creating or updating tenant artifacts using microservices. A multi-tenant cloud service provides a loosely-coupled and distributed approach for consistently creating or updating tenant artifacts through the use of multiple independent microservice's lifecycle containers, each having their own requirements during the creation or update of a tenant instance. The development and packaging of lifecycle containers is simplified by managing the software code responsible for artifact creation or update within a microservice code repository. The system can use a deployment approach of loosely-coupled microservice lifecycle containers together with an infrastructure lifecycle service that coordinates tenant artifact creation/update across multiple microservices.