Hybrid Connection Pool with Tenant Sub-pools
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud-based microservices environments, tenant-specific connection pools lead to increased memory usage and database connections, while global connection pools result in prolonged authentication times, affecting response times.
Innovation Solution
Implementing a global connection pool with tenant-specific sub-pools, where connections can be transferred between sub-pools based on usage, allowing for efficient authentication and resource utilization by disconnecting and reassigning idle connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If tenant-specific connection pools are used, then authentication efficiency is improved, but memory usage and database connection overhead increase
Solution Approach 1:
The patent merges the advantages of tenant-specific and global connection pools by implementing a hybrid architecture where a global connection pool shares authenticated connections across multiple tenants, reducing redundant authentication while maintaining tenant isolation through virtualization. This combination resolves the contradiction by eliminating repeated authentication (reducing time loss) while using a single shared pool (reducing memory usage compared to separate pools per tenant).
Solution Approach 2:
The global connection pool serves multiple tenants simultaneously, making it a universal resource that can be shared across different tenants. The connection pool manager implements multi-functionality by handling authentication, connection management, and tenant isolation within a single system, thereby reducing overall memory overhead while maintaining authentication efficiency.
2Quantity of substance
If global connection pools are used, then memory usage is reduced, but authentication times increase
Solution Approach 1:
The system performs preliminary authentication by pre-authenticating connections in the global connection pool before they are assigned to specific tenants. The connection pool manager maintains authenticated connection states in advance, so when tenants need connections, the authentication has already been completed. This preliminary action resolves the contradiction by reducing authentication time while maintaining a single global pool for memory efficiency.
Solution Approach 2:
The global connection pool implements self-service mechanisms where the connection pool manager automatically manages connection allocation, authentication state tracking, and tenant assignment without requiring manual intervention. This automation reduces authentication delays while maintaining efficient memory usage through centralized management.
3Productivity
If tenant-specific connection pools are used, then authentication efficiency is improved, but device complexity increases
Solution Approach 1:
The patent segments the connection pool management functionality into distinct modules: a global connection pool for shared authenticated connections, tenant-specific sub-pools for isolated connection tracking, and a connection pool manager for coordinating between them. This segmentation resolves the contradiction by maintaining authentication efficiency through structured organization while managing complexity through modular design with clear separation of concerns.
Data Source
AI summary
In order to address the technical problems encountered with tenant-specific connection pools and global connection pools, in an example embodiment, an efficient connection pool is provided, which restricts the total number of connections per application runtime instance (as with the global connection pool) but at the same time groups and maintains the connections at the tenant level, using tenant-specific sub-pools.