IVR Microservice Evaluation for Isolated Testing and Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Microservice operations in IVR systems are difficult to test without impacting other services, requiring maintenance windows that disrupt user interactions and necessitate offline testing, leading to inefficiencies and resource wastage.
Innovation Solution
A system and method to evaluate and update microservices individually within IVR operations, allowing for isolated testing and updates without affecting other services, using an admin server to manage and route evaluation requests through sub-dialogs, and provide feedback for response matching and updating.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If microservice operations are tested during maintenance window, then testing can be performed, but user interactions are disrupted and microservices must be taken offline
Solution Approach 1:
The system segments the monolithic microservice testing approach into individual microservice evaluation. Each microservice can be evaluated independently through its specific dialog or sub-dialog, allowing selective testing without taking the entire system offline. This segmentation enables continuous operation of unaffected microservices while maintaining testing capability for the specific service being evaluated.
Solution Approach 2:
The system introduces an intermediary evaluation mechanism that routes evaluation requests through specific dialogs or sub-dialogs associated with individual microservices. This intermediary layer allows testing traffic to be directed to specific microservices without affecting the overall system availability, enabling concurrent testing and user interaction.
2Adaptability or versatility
If all microservices are updated at once, then comprehensive updates are achieved, but system complexity and risk increase significantly
Solution Approach 1:
The update process is segmented into individual microservice updates rather than bulk updates. Each microservice can be evaluated and updated independently through its associated dialog, allowing incremental adoption of updates. This reduces system complexity by isolating update operations to specific services while maintaining the ability to comprehensively update all services over time through repeated individual updates.
Solution Approach 2:
The system performs preliminary evaluation of individual microservices before updating them. Each microservice undergoes evaluation through its specific dialog to assess readiness and compatibility before being updated. This preliminary action allows updates to be prepared and tested in isolation before deployment, reducing overall system complexity and risk while achieving comprehensive updates through sequential processing.
3Loss of energy
If microservices are evaluated in isolation, then resource usage is reduced and stability is maintained, but evaluation process becomes more complex
Solution Approach 1:
The evaluation process is segmented into microservice-specific dialogs or sub-dialogs, allowing evaluation traffic to be directed to individual services. This segmentation reduces resource usage by concentrating evaluation loads on specific microservices rather than overwhelming the entire system. The complexity is managed through automated routing mechanisms that map evaluation requests to appropriate service dialogs.
Solution Approach 2:
Each microservice evaluates itself through its associated dialog or sub-dialog, maintaining autonomy and reducing the need for centralized evaluation coordination. This self-service approach reduces overall system resource usage while managing complexity through standardized evaluation interfaces that each microservice implements independently.
4Loss of time
If maintenance window is used for testing, then dedicated testing time is provided, but downtime and user impact increase
Solution Approach 1:
The system implements periodic evaluation of individual microservices through their respective dialogs rather than requiring periodic maintenance windows. This allows continuous, distributed evaluation across multiple services over time, eliminating the need for集中 maintenance downtime while providing adequate testing opportunities for each microservice.
Solution Approach 2:
The evaluation process maintains continuity by allowing user interactions and microservice operations to proceed while evaluations occur in parallel through specific dialogs. This continuous operation eliminates downtime associated with traditional maintenance windows while ensuring adequate testing time is allocated through concurrent evaluation processes.
Data Source
AI summary
An apparatus may comprise a memory communicatively coupled to a processor. The processor may be configured to receive an evaluation request to perform multiple data processing operations; determine a microservice configured to fulfill the first evaluation request; and determine multiple publishing commands associated with the microservice. The one or more microservices may be integrated in multiple Interactive Voice Response (IVR) operations. The processor may be further configured to obtain input parameters of the one or more input parameters corresponding to the microservice; generate a response to the evaluation request associated with the microservice, compare the response to an expected response of the one or more expected responses; and determine whether the response matches the expected response. In response to determining that the response does not match the expected response, the processor is configured to update the publishing commands in accordance with multiple rules and policies, and publish the microservice.