Common Binary Directory for Application Server Clusters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing multi-tiered client-server architecture is inefficient for large enterprises due to the high cost of maintaining up-to-date client-side applications and the brittleness of client-side code, which is exacerbated by frequent changes in business logic. Additionally, the current method of storing separate binary files for each server node in a cluster consumes excessive storage space and network bandwidth.
Innovation Solution
Implementing a system that uses a common binary directory structure to store and manage binary files for multiple application server clusters, allowing for centralized storage and shared loading of binaries across all server nodes, reducing redundancy and improving efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate binary files are stored for each server node in a cluster, then each server node can independently load and execute binaries, but storage space and network bandwidth are consumed excessively due to redundancy
Solution Approach 1:
The patent merges the binary storage functionality across all server nodes by introducing a shared file system that stores binaries centrally. Instead of each node maintaining separate binary copies, all nodes access the same binary repository through the shared file system, eliminating redundancy while preserving independent loading capability through on-demand retrieval.
Solution Approach 2:
The shared file system serves multiple functions: it acts as a central binary repository for all server nodes, provides a caching mechanism to reduce repeated downloads, and enables inter-node binary sharing. This universal storage infrastructure replaces the need for separate binary storage on each node while supporting all original requirements.
2Reliability
If separate binary files are stored for each server node in a cluster, then each server node has full binary availability, but network bandwidth is consumed excessively during binary distribution and updates
Solution Approach 1:
The patent combines the binary distribution infrastructure into a single shared file system accessible by all nodes. When binaries need to be distributed or updated, they are transferred once to the shared file system rather than being pushed to each node individually, dramatically reducing network bandwidth consumption while maintaining binary availability through the shared access mechanism.
Solution Approach 2:
The shared file system pre-loads and caches binaries that are likely to be needed by server nodes. This preliminary action ensures that when nodes need binaries, they are already available in the shared system, reducing the need for repeated network transfers and bandwidth consumption during operation.
3Device complexity
If client-side applications are maintained with tight coupling of business logic, presentation logic and user interface logic, then the application structure is simple, but the client-side code becomes brittle and difficult to maintain
Solution Approach 1:
The patent segments the monolithic client-side application into distinct layers: presentation logic, business logic, and user interface logic. Each layer is separated into independent components that can be developed, maintained, and updated independently. The presentation logic layer communicates with business logic through well-defined interfaces, reducing brittleness while maintaining overall system coherence.
Solution Approach 2:
The patent introduces a new dimensional organization to the application structure by separating concerns across different logical layers rather than mixing them in a single codebase. This dimensional separation allows changes in one layer (e.g., business logic) to be isolated from others (e.g., user interface), improving maintainability without significantly increasing structural complexity.
4Adaptability or versatility
If the client-side user interface is changed in a multi-tiered architecture, then user interface flexibility is improved, but business logic may break due to tight coupling
Solution Approach 1:
The patent segments the application into distinct layers with clear boundaries. The presentation logic layer, which handles user interface rendering, is separated from the business logic layer. This segmentation allows user interface changes to be confined to the presentation layer without propagating to business logic, maintaining stability while enabling flexibility.
Solution Approach 2:
The patent introduces an intermediary layer (presentation logic) between the user interface and business logic. This intermediary handles all communication and data transformation, ensuring that changes in the user interface do not directly impact business logic. The intermediary maintains stable interfaces while allowing flexibility in both layers independently.
Data Source
AI summary
A system and method are described for managing a plurality of application servers. In one embodiment, the application servers are organized into groups referred to as “instances.” Each instance includes a group of redundant application servers and a dispatcher for distributing service requests to each of the application servers. In addition, a central message passing architecture is defined which allows the various instances to communicate with one another. In one embodiment, a hierarchical configuration data object is stored within a database and is centrally accessible by all of the servers from all of the instances. The hierarchical configuration data object organizes stores binary data (e.g., *.jar files) within a common binary directory and series of sub-directories, thereby simplifying application server management in an enterprise network.