Cloud Integration Database Connection Pools for Timeout Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Differing durations of database connection usage between integration flows and internal services in an integration platform create challenges, leading to connection timeouts and compromised internal service functions, affecting the execution of integration flows.
Innovation Solution
Implementing an internal data source with a reserved connection and an integration flow data source, both managed by a common name data source, to allocate connections based on request origin, ensuring availability for both integration flows and internal services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If a common pool of database connections is shared between integration flows and internal services, then connection pool utilization is improved, but connection timeout and service reliability deteriorate due to differing usage durations
Solution Approach 1:
The patent divides the common connection pool into separate dedicated pools: one for integration flows and one for internal services. This segmentation ensures that integration flows cannot consume all connections and cause timeouts for internal services, while still maintaining efficient connection utilization within each segment.
Solution Approach 2:
The patent applies different connection pool configurations and management strategies tailored to the specific needs of integration flows versus internal services. Each pool is optimized for its intended usage pattern, with internal services receiving guaranteed connections for critical operations while integration flows use a shared pool for batch operations.
2Duration of action of moving object
If database connections are allocated to integration flows for long-duration operations, then integration flow functionality is improved, but internal service connection availability deteriorates
Solution Approach 1:
By segmenting the connection pool into dedicated portions for integration flows and internal services, the system allows integration flows to hold connections for extended periods without impacting internal service availability. The internal services have their own guaranteed connection pool that cannot be consumed by integration flows.
Solution Approach 2:
The system pre-allocates a dedicated connection pool for internal services before integration flows can consume connections. This preliminary allocation ensures that critical internal services always have available connections, regardless of how many connections integration flows are using.
3Loss of time
If database connections are allocated to internal services for short-duration operations, then service response time is improved, but integration flow connection availability deteriorates
Solution Approach 1:
The segmented connection pool architecture allows internal services to have immediate access to their dedicated pool for fast, short-duration operations, while integration flows access a separate pool. This eliminates competition for connections and ensures both can operate efficiently at their respective pace.
Data Source
AI summary
Various examples described herein are directed to an integration platform system. The integration platform system may comprise a database management system and an integration flow worker. The integration flow worker may comprise an integration flow data source and an internal data source. The integration flow worker may receive, from a first integration flow, a first connection request for the database management system. The integration flow worker may assign a first connection from the integration flow connection pool to the first integration flow. The integration flow worker may receive, from an internal service, a second connection request describing a second operation to be performed at the database management system and assigning a reserved connection to the internal service.