Abstract: A method is described for on-demand creation of a database service. In response to receiving indication that the database service is to be created, an automated process is initiated, including instantiating a quantity of database servers. The database servers include a first subset of at least one of the database servers designated to handle read queries only, and a second subset of at least one of the database servers designated to handle write queries. The process includes determining a quantity and size of load-balancing proxies to instantiate for supporting the database server instance, and instantiating the determined quantity of load-balancing proxies of the determined size. At least one of the load-balancing proxies is a proxy configured to receive database queries and perform query routing among the first subset and the second subset, where one criterion for the query routing is whether a given query is a read or write query.

Abstract: A system and method can support using a data source to connect an application server with a clustered database. The clustered database includes a plurality of database instances and is associated with a notification service. The notification service can be used by the clustered database to broadcast notifications that describe a state change in the plurality of database instances. The data source includes a connection pool, which manages a set of connections to the plurality of database instances in the clustered database. The data source operates to register with the notification service to receive notifications on the change of the clustered database, wherein the application server operates to configure and manage connection to the clustered database, adaptively according to the state change of the clustered database at run time.

Abstract: Runtime connection load balancing of work across connections to a clustered computing system involves the routing of requests for a service, based on the current operational performance of each of the instances that offer the service. A connection is selected from an identified connection pool, to connect to an instance that provides the service for routing a work request. The operational performance of the instances may be represented by performance information that characterizes the response time and/or the throughput of the service that is provided by a particular instance on a respective node of the system, and is relative to other instances that offer the same service.

Abstract: Techniques for routing client requests among a group of nodes offering a service are described. A coordinator determines that performance could be improved by using affinity-based routing. In one embodiment, the coordinator calculates a Time-to-Live (TTL) metric whereby clients benefit by returning to the same cache and posts this hint to subscribers. Client's start preserving locality data in an affinity context, such that later requests for a connection can be routed to the location last visited. The coordinator measures the system over subsequent intervals. If the gradient of the goodness (viz service quality and capacity) is stable or improving, then the coordinator continues to advise subscribers to use the affinity-based technique. Alternatively, if the gradient of the goodness is deteriorating, then the coordinator posts advice to the subscribers to stop using the affinity-based technique for any instance during the next intervals.

Abstract: A system and method can support using a data source to connect an application server with a clustered database. The clustered database includes a plurality of database instances and is associated with a notification service. The notification service can be used by the clustered database to broadcast notifications that describe a state change in the plurality of database instances. The data source includes a connection pool, which manages a set of connections to the plurality of database instances in the clustered database. The data source operates to register with the notification service to receive notifications on the change of the clustered database, wherein the application server operates to configure and manage connection to the clustered database, adaptively according to the state change of the clustered database at run time.

Abstract: Techniques for fast recovery and/or balancing of connections to a clustered computing system provide management of such connections by determining a number of connections to load balance across nodes and by triggering creation of such connections. In one aspect, a notification of an event regarding the clustered computing system is received by a connection pool manager, a pool of connections to the system is identified based on the notification, and one or more connections from the pool are processed in response to the event. According to an embodiment, the notification comprises the identities of the service, database, server instance and machine that correspond to the event.

Abstract: Runtime connection load balancing of work across connections to a clustered computing system involves the routing of requests for a service, based on the current operational performance of each of the instances that offer the service. A connection is selected from an identified connection pool, to connect to an instance that provides the service for routing a work request. The operational performance of the instances may be represented by performance information that characterizes the response time and/or the throughput of the service that is provided by a particular instance on a respective node of the system, and is relative to other instances that offer the same service.

Abstract: Runtime connection load balancing of work across connections to a clustered computing system involves the routing of requests for a service, based on the current operational performance of each of the instances that offer the service. A connection is selected from an identified connection pool, to connect to an instance that provides the service for routing a work request. The operational performance of the instances may be represented by performance information that characterizes the response time and/or the throughput of the service that is provided by a particular instance on a respective node of the system, and is relative to other instances that offer the same service.

Abstract: Techniques for routing client requests among a group of nodes offering a service are described. A coordinator determines that performance could be improved by using affinity-based routing. In one embodiment, the coordinator calculates a Time-to-Live (TTL) metric whereby clients benefit by returning to the same cache and posts this hint to subscribers. Client's start preserving locality data in an affinity context, such that later requests for a connection can be routed to the location last visited. The coordinator measures the system over subsequent intervals. If the gradient of the goodness (viz service quality and capacity) is stable or improving, then the coordinator continues to advise subscribers to use the affinity-based technique. Alternatively, if the gradient of the goodness is deteriorating, then the coordinator posts advice to the subscribers to stop using the affinity-based technique for any instance during the next intervals.

Abstract: Techniques for obtaining a closest match connection to a resource (e.g., a database) from a cache are provided. The request specifies desired attribute values for the connection and a closest match connection is identified. The attributes can have associated weights that are utilized in order to determine the closest match connection to satisfy the connection request.

Abstract: Techniques for implicitly caching connections to a resource (e.g., a database) are provided. A request for a connection does not specify that available connections are stored in a cache. If available connections are stored in a cache, the connection to the resource is obtained from the cache. Otherwise, a new connection to the resource is opened directly, without a connection caching mechanism.

Abstract: Techniques for utilizing a time-to-live timeout on a logical connection to a resource (e.g., a database) from a cache are provided. When a logical connection to the resource is obtained, a timeout is set specifying the amount of time the logical connection can be utilized. If the timeout expires, the logical connection is closed and the underlying physical connection can be returned to the cache.

Abstract: Runtime connection load balancing of work across connections to a clustered computing system involves the routing of requests for a service, based on the current operational performance of each of the instances that offer the service. A connection is selected from an identified connection pool, to connect to an instance that provides the service for routing a work request. The operational performance of the instances may be represented by performance information that characterizes the response time and/or the throughput of the service that is provided by a particular instance on a respective node of the system, and is relative to other instances that offer the same service.

Abstract: Techniques for fast recovery and/or balancing of connections to a clustered computing system provide management of such connections by determining a number of connections to load balance across nodes and by triggering creation of such connections. In one aspect, a notification of an event regarding the clustered computing system is received by a connection pool manager, a pool of connections to the system is identified based on the notification, and one or more connections from the pool are processed in response to the event. According to an embodiment, the notification comprises the identities of the service, database, server instance and machine that correspond to the event.

Abstract: Techniques for implicitly caching connections to a resource (e.g., a database) are provided. A request for a connection does not specify that available connections are stored in a cache. If available connections are stored in a cache, the connection to the resource is obtained from the cache. Otherwise, a new connection to the resource is opened directly, without a connection caching mechanism.

Abstract: Techniques for utilizing a time-to-live timeout on a logical connection to a resource (e.g., a database) from a cache are provided. When a logical connection to the resource is obtained, a timeout is set specifying the amount of time the logical connection can be utilized. If the timeout expires, the logical connection is closed and the underlying physical connection can be returned to the cache.

Abstract: Techniques for obtaining a closest match connection to a resource (e.g., a database) from a cache are provided. The request specifies desired attribute values for the connection and a closest match connection is identified. The attributes can have associated weights that are utilized in order to determine the closest match connection to satisfy the connection request.