Parallel Mesh Virtual Dependency Caching for Faster Application Builds

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developers face challenges in efficiently managing dependency information for application development, which requires local storage, consumes network resources, and involves time-consuming processes, especially when multiple developers are involved.

Innovation Solution

A computing platform with a smart contract system manages dependency information across a distributed parallel mesh network, allowing nodes to transmit virtual copies of packages without local storage, optimizing resource usage and enabling parallel processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If dependency information is locally stored by developers, then application development can proceed, but local disc space is consumed and network bandwidth is used

Engineering Contradiction:
Improveapplication development efficiencyVSAvoidlocal disc space consumption
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent creates virtual copies of dependency packages that are transmitted over the network and stored in a distributed cache system. These virtual copies allow developers to access dependency information without storing full local copies, thereby reducing local disc space consumption while maintaining development efficiency.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces a distributed cache system as an intermediary between the central repository and developer machines. This intermediary stores virtual copies of dependency packages and serves them to developers, reducing both local storage requirements and network bandwidth consumption by caching frequently accessed dependencies.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If dependency information is locally stored by multiple developers, then each can develop independently, but space and network resources are consumed multiply

Engineering Contradiction:
Improveindependent development capabilityVSAvoidtotal space and network resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges the storage capacity of multiple developer machines into a shared distributed cache system. Instead of each developer maintaining separate local copies of dependency packages, the system combines their storage resources to create a collective cache that serves all developers, thereby reducing total space consumption and network bandwidth usage.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The distributed cache system serves multiple functions: it acts as a local cache for each developer, a shared repository for the team, and a buffer between the central repository and developer machines. This multi-functionality allows the system to reduce resource consumption while maintaining independent development capability for all developers.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of operation

If dependency packages are transmitted to each developer locally, then development can proceed, but network bandwidth and time are consumed

Engineering Contradiction:
Improvedevelopment process smoothnessVSAvoidtime to obtain dependency information
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent pre-transmits and caches virtual copies of dependency packages in the distributed cache system before they are needed by developers. This preliminary action ensures that when developers need dependency information, it is already available in the distributed cache, eliminating download delays and maintaining smooth development processes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The distributed cache system maintains continuous availability of dependency packages by keeping virtual copies cached and ready for immediate access. This continuity eliminates the need for repeated downloads from the central repository, reducing time loss and maintaining uninterrupted development workflows.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS20250217135A1Intelligent Systems for Autogenerating Disseminated Virtual Environment Setup Using Parallel Mesh Oriented Logical Programming
Publication Date: 2025.07.03 BANK OF AMERICA CORP
  • US20250217135A1 patent drawing
  • US20250217135A1 patent drawing
  • US20250217135A1 patent drawing

AI summary

Arrangements for remotely developing an application are provided. A computing platform may receive a request to build an application. The computing platform may receive the request through an API gateway. The computing platform may use a smart contract to identify a first node as a parent node and a plurality of nodes as child nodes. The computing platform may direct the child nodes to transmit virtual copies of dependency packages to the parent node. The parent node may build the application after receiving the dependency packages. The computing platform may detect that the application has been successfully built and may automatically publish the application at an enterprise server.