PaaS Template Update Coordination for Enterprise Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing PaaS systems face challenges in efficiently updating software bundles across a large number of applications, as changes to one template can lead to misconfiguration and affect many applications, requiring a systematic and automated approach to manage updates without breaking applications.

Innovation Solution

The extensible PaaS system employs a method to coordinate updates to software bundles by identifying affected applications, grouping them, and applying updates in a controlled sequence, starting with test environments and then production, ensuring that updates are verified before being rolled out to all applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If template updates are applied directly to all applications, then update speed is improved, but application reliability deteriorates due to potential misconfiguration

Engineering Contradiction:
Improveupdate speedVSAvoidapplication reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by creating test applications and applying template updates to them before deploying to production applications. This allows validation of template updates in a safe environment, ensuring reliability while maintaining update capability. The test applications serve as a preliminary testing ground to catch potential misconfigurations before they affect real applications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system segments applications into different groups (test applications and production applications) and applies updates in a staged manner. By dividing the deployment process into separate phases with different application sets, the system can control the spread of potential errors while maintaining overall update progress across the enterprise application portfolio.

Inventive Principle:
Principle #1Segmentation

2Reliability

If manual verification is performed for each application update, then update reliability is improved, but time consumption increases

Engineering Contradiction:
Improveupdate verification reliabilityVSAvoidupdate deployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system creates copies of production applications as test applications. These copies allow automated verification of template updates without affecting the original production applications. The copying approach enables parallel testing and validation, significantly reducing the time required for manual verification while maintaining reliability through automated test execution.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system implements self-service through automated verification processes that automatically test template updates on test applications and determine whether updates are safe for production deployment. This automated self-verification eliminates the need for time-consuming manual checks while maintaining high reliability through systematic automated testing and validation.

Inventive Principle:
Principle #25Self-service

3Reliability

If template changes are made to fix security issues, then security reliability is improved, but application stability deteriorates due to potential misconfiguration

Engineering Contradiction:
Improvesecurity reliabilityVSAvoidapplication stability
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The system applies security template updates to test applications in advance before deploying to production applications. This preliminary application allows security fixes to be validated in a controlled environment, ensuring security reliability is improved while preventing stability issues from propagating to production systems. The test applications act as a buffer to catch potential misconfigurations before they affect stable production applications.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12340213B2Application and infrastructure template management to easily create secure applications for enterprises
Publication Date: 2025.06.24 SALESFORCE INC
  • US12340213B2 patent drawing
  • US12340213B2 patent drawing
  • US12340213B2 patent drawing

AI summary

An extensible platform-as-a-service (PaaS) system is used during the software development lifecycle (SDLC) processes of an application. The system, according to various embodiments, receives indications that changes are made to one or more templates or software bundles stored in a software library and coordinates how changes to a particular template will be applied to applications for an enterprise system. Specifically, the system may identify applications that are using the template and determine an ordering for a plurality of application groups that indicates a sequence in which the updates will be applied to the applications. In this manner, template updates can be automatically and systematically deployed to applications without significant involvement by users of the PaaS system.