Segregated Rule Schemas for Zero-Downtime Code Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Code deployment and business validation in systems like PEGA-based BPM systems often require significant downtime, necessitating off-hours deployment to minimize user application disruption.
Innovation Solution
A computer system with segregated schemas for user and developer environments, allowing updates to be applied without affecting the user application, using a processor to manage schema changes and validation checks, and implementing encryption and decryption protocols for secure data handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If code deployment is performed in a traditional single-schema system, then the compiled code base can be updated, but the user application must be taken offline resulting in downtime
Solution Approach 1:
The patent segments the compiled code base into two separate rule schemas: a first rule schema for production use and a second rule schema for development and validation. This segmentation allows the user application to continue using the first rule schema while the second rule schema is updated and validated, eliminating deployment downtime and maintaining system availability.
Solution Approach 2:
The patent implements preliminary action by performing code updates and business validations in the second rule schema before they affect the production environment. Developers can update the compiled code base and validate changes in the second rule schema in advance, ensuring readiness before switching to the updated schema, thus preventing any service interruption.
2Productivity
If developers update the compiled code base directly in the production schema, then deployment can be performed, but validation cannot occur without affecting user operations
Solution Approach 1:
The patent segments the development and production environments into separate rule schemas. The second rule schema serves as a dedicated development and validation environment where developers can update and validate the compiled code base without interfering with production operations. This segmentation enables simultaneous development validation and production stability.
Solution Approach 2:
The second rule schema acts as an intermediary between development and production. It provides a buffer zone where code changes can be validated using the same data schema as production, ensuring compatibility and safety before the changes are promoted to the first rule schema for production use.
3Loss of time
If a segregated schema architecture is implemented, then zero-downtime deployment is enabled, but system complexity increases
Solution Approach 1:
The patent merges the development and production rule schemas in terms of data access by pointing both schemas to the same data schema. This allows validators to use production data for validation purposes while keeping the rule logic separate. The merging of data access paths simplifies the overall architecture compared to maintaining completely separate data environments.
Data Source
AI summary
A computer system includes a database configured to store a first rule schema, a second rule schema and a data schema, the first and second rule schemas each configured to store a compiled code base, and the data schema configured to store transactional data. The system includes a user application node configured to allow users to perform application operations, and a developer application node configured to facilitate developer deployment operations. Processor hardware is configured to point the user application node to the first rule schema, point the developer application node to the second rule schema, point the user application node and the developer application node to the data schema, update the second rule schema according to updates received via the developer application node, and in response to validation of the updates to the second rule schema, change the user application node to point to the updated second rule schema.