Multi-tenancy Connection Manager Throttling for Service Quality

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-tenancy computing environments, a single tenant's excessive requests or long-held connections can degrade the quality of service for other tenants, leading to 5xx errors due to limited connection capacity, as existing systems lack tenant-aware connection management strategies.

Innovation Solution

Implementing a multi-tenancy connection manager that configures and monitors individual connection pools for each tenant, allowing dynamic scaling and enforcing management rules to throttle requests and maintain service quality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If connection limits are imposed to prevent tenant A from exhausting server resources, then other tenants can access servers, but tenant A's legitimate requests may be blocked

Engineering Contradiction:
Improveservice availability for all tenantsVSAvoidconnection request acceptance
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments the shared connection pool into separate connection pools for each tenant. Each tenant has their own dedicated connection pool, which isolates their connection usage from other tenants. This segmentation allows the system to enforce connection limits per tenant without affecting other tenants' access to the server.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a connection manager as an intermediary component between tenants and the server. The connection manager allocates connections from appropriate pools based on tenant identification, enforces connection limits, and mediates connection requests. This intermediary enables the system to distinguish between different tenants and their connection needs.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If connection pools are created for each tenant to isolate resources, then service quality for individual tenants is maintained, but system complexity increases

Engineering Contradiction:
Improvequality of service per tenantVSAvoidconnection management structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The connection manager serves multiple functions: it identifies tenants from requests, selects appropriate connection pools, enforces connection limits, and manages connection allocation. By consolidating these functions into a single multi-functional component, the patent reduces overall system complexity while maintaining per-tenant resource isolation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Object-affected harmful factors

If connection limits are enforced to prevent server overload, then server resources are protected, but legitimate tenant requests are rejected

Engineering Contradiction:
Improveserver resource exhaustionVSAvoidconnection request throughput
Core Design Contradiction:
Object-affected harmful factorsVSProductivity

Solution Approach 1:

By segmenting connections into per-tenant pools, the system can enforce connection limits at the tenant level rather than at the server level. This allows the system to protect server resources from any single tenant while still allowing legitimate requests from all tenants to proceed through their dedicated pools.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12101256B1Managing connections in a multi-tenancy computing environment
Publication Date: 2024.09.24 FRESHWORKS INC
  • US12101256B1 patent drawing
  • US12101256B1 patent drawing
  • US12101256B1 patent drawing

AI summary

A method of managing connections to one or more servers in a multi-tenancy computing environment is provided. At a multi-tenancy connection manager responsible for managing connections for multiple tenants of the multi-tenancy computing environment, a plurality of connection pools is configured, each for use by a respective one of the multiple tenants. A connection request is received from a tenant of the multiple tenants. The tenant is identified based on the connection request. Management rules for managing a connection pool that is associated with the identified tenant are obtained. It is determined whether the management rules permit execution of the connection request. In response to a positive determination, the connection request is executed. In response to a negative determination, the connection request is throttled, to preserve and maintain a quality of service provided.