Cloud Portability Code Scanning Tool for Vendor Lock-in

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The migration of applications to cloud platforms often results in vendor lock-in due to tight coupling and lack of consideration for cloud infrastructure portability, making it difficult and costly to move workloads across different vendors.

Innovation Solution

A cloud portability code scanning tool that assesses application code against a cloud portability index, identifying dependencies on cloud provider artifacts and providing recommendations to avoid vendor lock-in, integrated into the software development lifecycle through plugins for IDEs and other code scanning tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If applications are migrated to cloud platforms at high speed, then productivity and availability are improved, but vendor lock-in and tight coupling increase

Engineering Contradiction:
Improvemigration speedVSAvoidcloud portability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by scanning application code before deployment to identify cloud provider-specific dependencies and generate portability recommendations in advance. This allows developers to refactor code proactively during the development phase rather than reactively during migration, enabling high-speed migration while maintaining portability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback through automated code scanning that analyzes application dependencies against cloud provider artifacts, generates portability scores, and provides actionable recommendations. This feedback loop enables continuous improvement of code portability during the development and migration processes.

Inventive Principle:
Principle #23Feedback

2Productivity

If code is written without cloud portability consideration, then development speed is improved, but refactoring cost increases

Engineering Contradiction:
Improvedevelopment speedVSAvoidrefactoring time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by performing code scanning and portability assessment during the development phase before deployment. This early detection of portability issues prevents costly refactoring later by enabling developers to address dependencies proactively, thus maintaining high development speed while minimizing refactoring time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by providing real-time portability scores and recommendations during the development process. This feedback mechanism guides developers to write more portable code from the outset, reducing the need for expensive and time-consuming refactoring in later stages.

Inventive Principle:
Principle #23Feedback

3Reliability

If cloud provider artifacts are used, then functionality is improved, but vendor lock-in increases

Engineering Contradiction:
Improvefunctional capabilityVSAvoidvendor independence
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements feedback by scanning application code for cloud provider-specific artifacts and dependencies, generating portability scores that quantify vendor lock-in risk. This feedback enables organizations to maintain functional capability through cloud provider artifacts while identifying and mitigating vendor lock-in risks through automated analysis and recommendations.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12001815B2Cloud portability code scanning tool
Publication Date: 2024.06.04 JPMORGAN CHASE BANK NA
  • US12001815B2 patent drawing
  • US12001815B2 patent drawing
  • US12001815B2 patent drawing

AI summary

Embodiments disclosed herein provide for systems and methods for scanning application code to determine cloud platform portability. The systems and methods provide for a rules processing engine configured to perform a portability analysis on the application code and a list of cloud platform dependencies, and returns a score indicating the “stickiness” of the application code to a particular cloud platform.