Skip to content

[FEATURE]: Redesign Connection Management for Better Pooling and Context Isolation #3187

@jac0626

Description

@jac0626

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe.

Description:
The current Connections singleton mixes configuration (aliases) with active connection state. As we move towards a stateless GrpcHandler, the connection management layer needs to be fundamentally redesigned to better support:

  1. True Pooling: Manage a pool of underlying gRPC channels that can be borrowed.
  2. Context Isolation: Ensure that user-specific context (like db_name, user, role) is applied at the request level, not the connection level.
  3. Health Checks: Better active health monitoring of connections.

Note: This is a long-term refactoring goal that builds upon the work of making GrpcHandler stateless .

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Anything else?

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions