In-Memory Data Grid Container for WebLogic Multi-Tenancy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Organizations using in-memory data grids face challenges in effectively managing their data grid applications and associated environments, often relying on third-party management tools or custom infrastructure.
Innovation Solution
A system and method for providing an in-memory data grid application container that allows an application server, such as WebLogic Server, to host data grid applications like Coherence, enabling multi-tenancy and merging programming, packaging, and deployment models with Java Enterprise Edition (EE) models to create combined JEE and data grid applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If third-party management tools or custom infrastructure are used to manage data grid applications, then data grid applications can be managed, but the system complexity and operational overhead increase
Solution Approach 1:
The patent merges data grid application management into the application server's native container infrastructure. The data grid application is packaged as a standard Java EE application archive (EAR, WAR, or JAR) that can be deployed using the application server's existing deployment mechanisms, eliminating the need for separate third-party management tools or custom infrastructure.
Solution Approach 2:
The application server container is enhanced to provide universal support for both traditional Java EE applications and data grid applications through a unified deployment model. The same container infrastructure that hosts standard EE applications now also natively hosts data grid applications, allowing the system to perform multiple functions through a single platform.
2Adaptability or versatility
If data grid applications are deployed without a unified container model, then data grid functionality can be provided, but integration with Java EE lifecycle management and deployment processes is lost
Solution Approach 1:
The container is designed to universally handle both Java EE applications and data grid applications through a single unified interface. The deployment descriptor and lifecycle management mechanisms are standardized to work with both application types, ensuring consistent integration with Java EE models while maintaining reliability through proven enterprise-grade management processes.
Solution Approach 2:
The patent segments the data grid application into standard Java EE deployable units (EAR, WAR, JAR archives) that can be independently managed through the application server's deployment pipeline. This segmentation allows data grid applications to be integrated into existing Java EE lifecycle management while maintaining their functional integrity.
3Productivity
If multiple isolated data grid applications are hosted on a single cluster, then resource utilization improves, but isolation and security between applications become more challenging
Solution Approach 1:
The patent implements segmentation through application-specific class loaders and namespace isolation within the container. Each deployed application archive receives its own isolated class loading context and runtime environment, ensuring that multiple data grid applications can coexist on the same cluster with proper isolation boundaries for security and reliability.
Solution Approach 2:
The application server container provides a nested hierarchical structure where isolated application environments are nested within the shared cluster infrastructure. Each application runs in its own isolated context (nested layer) while utilizing shared cluster resources (outer layer), achieving both high resource utilization and strong application isolation.
Data Source
AI summary
A system and method for providing an in-memory data grid application container, for use with an application server, is described herein. In accordance with an embodiment, an application server, such as WebLogic Server (WLS), can be used to host data grid applications, such as Coherence applications (in which case the application container can be referred to as a Coherence container), and deliver the same benefits that regular Java Enterprise Edition (EE) applications derive from being hosted in a WLS environment. A model for creating combined Java EE and data grid applications can also be provided, by merging the programming, packaging, and deployment models used for data grid with existing Java EE models.