Dynamic Property Bus for Autoscaling Cloud Instances

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In a distributed cloud environment with autoscaling, it is challenging to propagate application properties to an unknown number of instances, leading to difficulties in updating all running instances efficiently and avoiding outages.

Innovation Solution

A method is introduced that generates a dynamic property bus interface to write and propagate application property values to a database, which are then read and updated by each instance's scheduler, ensuring real-time updates across all instances without requiring instance recycling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional endpoint-based property propagation is used, then properties can be pushed to known instances, but it fails to reach all instances in an autoscaling environment where the number of instances is unknown

Engineering Contradiction:
Improveadaptability to autoscalingVSAvoidcompleteness of property propagation
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

Instead of pushing properties from the central service to instances (traditional approach), the patent inverts the approach by having instances pull properties from the database. Each instance executes a scheduler that periodically reads the latest property values directly from the database, ensuring all instances receive updates regardless of when they were created or scaled.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

Each application instance autonomously retrieves its own property values by executing a scheduler that reads from the database. This self-service mechanism eliminates the need for the central service to track and push properties to each instance individually, making the system adaptable to dynamic scaling while ensuring complete property propagation.

Inventive Principle:
Principle #25Self-service

2Reliability

If application properties are updated by recycling instances, then all instances are updated, but this causes service outages and interruptions

Engineering Contradiction:
Improvecompleteness of property updateVSAvoidservice availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements a scheduler in each instance that proactively and periodically reads property values from the database before any updates are needed. This preliminary action ensures that when property changes occur in the database, all running instances will detect and apply these changes during their next scheduled read, without requiring instance recycling or causing service interruptions.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If manual property propagation to each instance is implemented, then all instances can be updated, but this requires significant developer intervention and is inefficient

Engineering Contradiction:
Improvecompleteness of property propagationVSAvoidautomation of property propagation
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

Each application instance autonomously retrieves its own property values by executing a scheduler that reads from the database. This self-service mechanism eliminates the need for the central service to track and push properties to each instance individually, making the system adaptable to dynamic scaling while ensuring complete property propagation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The scheduler in each instance provides feedback by periodically checking the database for property changes and automatically applying updates when detected. This automated feedback loop eliminates manual developer intervention while ensuring all instances receive complete property propagation, as each instance independently monitors and applies updates.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11886861B2Propagating application properties to multiple instances
Publication Date: 2024.01.30 JPMORGAN CHASE BANK NA
  • US11886861B2 patent drawing
  • US11886861B2 patent drawing
  • US11886861B2 patent drawing

AI summary

In one example, a method for updating an application that has multiple instances running in a distributed cloud environment is disclosed. The method may include the operation of generating a dynamic property bus interface. The method may write an application property value through the dynamic property bus interface to a database for storage and propagate the property value to the multiple instances of the application in the distributed cloud environment.