Integration Flow Database Connections with Reserved Internal Service Access
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 efficiently allocate database connections based on the request's origin, ensuring adequate availability for both integration flows and internal services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Duration of action of moving object
If integration flows use database connections for extended periods to process messages, then integration flow processing is completed, but internal services experience connection timeouts and cannot execute operations
Solution Approach 1:
The patent segments the database connection pool into two distinct pools: one dedicated to integration flows and another to internal services. This segmentation allows each type of operation to have guaranteed access to appropriate connection resources, preventing integration flows from monopolizing connections needed by internal services, thereby resolving the timeout issues while maintaining long connection durations for message processing.
Solution Approach 2:
The patent applies local quality by providing different connection pool characteristics to different callers: integration flows receive connections optimized for long-duration message processing, while internal services receive connections optimized for short-duration administrative operations. This localized optimization ensures each gets the connection properties it needs without compromising the other.
2Productivity
If a single shared database connection pool is used by both integration flows and internal services, then resource utilization is efficient, but connection availability for internal services is compromised when integration flows hold connections
Solution Approach 1:
The unified connection pool is segmented into separate pools for integration flows and internal services. This segmentation maintains high resource utilization by ensuring connections are always available to appropriate callers, while simultaneously guaranteeing connection availability for internal services regardless of integration flow activity levels.
Solution Approach 2:
The patent introduces an intermediary mechanism (the connection pool manager with differentiated access logic) that mediates between integration flows and internal services. This intermediary allocates connections from appropriate pools based on the caller type, ensuring internal services always have access to available connections while integration flows can efficiently process messages.
3Productivity
If database connections are allocated to integration flows without reservation for internal services, then integration flow processing capacity is maximized, but internal service functions are compromised
Solution Approach 1:
The connection pool is segmented with a dedicated portion reserved for internal services, allowing integration flows to maximize their processing capacity using the remaining connections. This segmentation ensures internal service functions remain reliable and uninterrupted regardless of integration flow activity levels.
Solution Approach 2:
The patent applies preliminary action by reserving connections for internal services in advance, before any integration flow processing begins. This pre-allocation ensures that when internal services need to execute administrative operations, connections are already available, preventing timeouts and maintaining function integrity.
Data Source
Figure 1
Figure 2
Figure 3
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.