CDN Java Framework Edge Deployment Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing content delivery networks (CDNs) lack the ability to efficiently deploy and execute Java-based enterprise applications at the edge of the Internet, leading to network latency and increased infrastructure costs.
Innovation Solution
A CDN Java application framework that enables the deployment and execution of Java-based applications, including Web and Enterprise tiers, on edge servers, utilizing Java-enabled edge servers with load-balancing and management systems, allowing for the offloading of application processing close to end-users.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Java-based enterprise applications are deployed on centralized origin servers, then application execution control and security are maintained, but network latency increases and infrastructure costs rise
Solution Approach 1:
The patent segments the application deployment architecture by distributing Java application components across multiple edge servers in the CDN network rather than concentrating them on centralized origin servers. This segmentation allows applications to be executed closer to end users while maintaining centralized control through the deployment manifest mechanism, thereby reducing network latency while preserving execution control.
Solution Approach 2:
The patent introduces a deployment manifest as an intermediary component that bridges the centralized origin server and distributed edge servers. The manifest contains instructions that enable origin servers to push application components to appropriate edge servers, and edge servers to execute them locally. This intermediary mechanism maintains security and control while enabling distributed execution.
2Productivity
If Java applications are distributed across multiple edge servers, then network latency is reduced and performance improves, but device complexity and deployment management increase
Solution Approach 1:
The patent implements self-service mechanisms where edge servers automatically receive deployment manifests from origin servers and autonomously deploy and execute Java application components based on the instructions in the manifests. This self-service approach eliminates the need for manual configuration and management of distributed applications, reducing deployment complexity while maintaining high performance.
Solution Approach 2:
The patent uses deployment manifests that contain configurable parameters and instructions for controlling application behavior across different edge servers. By changing parameters in the manifest, the system can dynamically control which applications are deployed to which edge servers, enabling flexible management without increasing operational complexity.
3Loss of energy
If edge servers execute Java application code locally, then infrastructure costs are reduced by offloading work from origin servers, but security risks increase from executing untrusted code at the edge
Solution Approach 1:
The patent applies preliminary action by having origin servers sign Java application components with digital signatures before pushing them to edge servers. The deployment manifest includes these signatures and verification instructions. Edge servers verify the signatures before executing the code, ensuring that only authenticated and authorized applications are deployed. This preliminary verification prevents security risks while enabling cost-effective distributed execution.
Solution Approach 2:
The patent implements feedback mechanisms where edge servers report execution status and security events back to origin servers. This feedback loop enables continuous monitoring and validation of distributed application execution, allowing the system to detect and respond to potential security issues while maintaining the cost benefits of edge execution.
Data Source
AI summary
An application deployment model for enterprise applications to enable applications to be deployed to and executed from a globally distributed computing platform, such as an Internet content delivery network (CDN). According to the invention, application developers separate their Web application into two layers: a highly distributed edge layer and a centralized origin layer. In a representative embodiment, the edge layer supports a servlet container that executes a Web tier, typically the presentation layer of a given Java-based application. Where necessary, the edge layer communicates with code running on an origin server to respond to a given request. In an alternative embodiment, the edge layer supports a more fully-provisioned application server that executes both Web tier (e.g., presentation) and Enterprise tier application (e.g., business logic) components. In either case, the inventive framework enables one or more different applications to be deployed to and executed from the edge server on behalf of one or more respective entities.