Local Code Evaluation for Cloud Deployment Error Checking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud platforms, such as the Salesforce platform, face challenges in comprehensive local code-base error checking, leading to delays and inefficiencies in the application development cycle due to reliance on compile-time error checking at the cloud platform, which hinders developer productivity and code quality.

Innovation Solution

Implementing a local code evaluation technique that enables error checking and tool processing to be performed locally at the developer's device, allowing for real-time error reporting, customized analysis, and reduced dependency on cloud-based synchronization, using a local development environment with components like code editors, dependency mappers, parsers, compilers, and evaluators.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If error checking is performed at cloud platform compile-time, then comprehensive error detection is achieved, but development cycle delays and reduced productivity occur

Engineering Contradiction:
Improveerror detection capabilityVSAvoiddeveloper productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary error checking by downloading cloud platform compiler tooling to the local development environment before code submission. This allows error detection to occur locally prior to cloud compilation, enabling developers to identify and fix errors without waiting for cloud platform feedback, thus resolving the contradiction between comprehensive error detection and development productivity

Inventive Principle:
Principle #10Preliminary action

2Reliability

If cloud-based compile-time checking is used, then error detection coverage is comprehensive, but response time instability and deployment failures increase

Engineering Contradiction:
Improveerror detection coverageVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

By performing error checking locally through downloaded cloud compiler tooling before code submission, the system eliminates the need to wait for cloud platform compilation feedback. This preliminary action stabilizes response times and reduces deployment failures by ensuring code is validated locally with the same tooling that will be used in the cloud, without incurring cloud compilation delays

Inventive Principle:
Principle #10Preliminary action

3Productivity

If local code evaluation is implemented, then developer experience and development efficiency improve, but dependency on cloud-based tooling must be maintained

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidlocal development environment complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent uses cloud platform compiler tooling as an intermediary that is downloaded to the local development environment. This intermediary provides comprehensive error checking capabilities locally while maintaining dependency on cloud-based tooling, as the downloaded tooling is obtained and managed through cloud platform interactions. This resolves the contradiction by enabling enhanced local evaluation without complete independence from cloud services

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11868231B2System and method for evaluating code by a hybrid of local and cloud-based computers
Publication Date: 2024.01.09 CERTINIA INC
  • US11868231B2 patent drawing
  • US11868231B2 patent drawing
  • US11868231B2 patent drawing

AI summary

A technique is described for evaluating code at a local computing device before deploying the code to a cloud computing platform to be compiled. In an example embodiment, class files including the code in a programming language associated with the cloud computing environment are loaded by a local computer system, for example, associated with a software developer. The local computer system then parses the code to identify elements in the code and checks the identified elements. Errors in the code are identified based on the checking and are displayed to a user (e.g., the developer), for example, via a graphical user interface of a code editor application.