Netsuite Inc.

Theodore Ray Rice

Christopher T Blum

David Lipscomb

Sean Patrick Fay

John Cherniavsky

Xi (Scott) Liu

Steven Ellis Rolls

Christian Marenbach

Methods, systems, and other embodiments for protecting a shared resource in a data processing system are described herein. In one embodiment, when responding to a request that requires use of the shared resource, determine whether a previously established sleep period for the shared resource has expired. If so, determine a health status of the shared resource based on one or more of applying an asymptotic transform to a percentage of time that a processing unit is idle and applying a linear transform to a session count for the shared resource. Then, determine whether the health status is sufficient to permit responding to the request; and if not, (i) determining an appropriate sleep period for the shared resource, (ii) initiating a sleep state for the shared resource for a period substantially equal to the determined appropriate sleep period; and (iii) exiting the sleep state and responding to the request.

Shared resources control in a multi-tenant system

Systems, apparatuses, and methods for preventing the use of a shared resource (such as a database) by a user or group of users from causing other users to experience unsatisfactory or unreliable access to that resource or to related, impacted resources (such as a communications network or processor). In some embodiments, the invention is directed to systems, apparatuses, and methods that may be implemented in a multi-tenant system in order to prevent a single user or the users associated with an account from degrading the system performance experienced by other users, either by intentional or inadvertant misuse of a shared database, and to prevent an overload condition from causing the system or database to fail abruptly.

System and methods for implementing control of use of shared resource in a multi-tenant system

A method, system, computer program product, and related business methods for phased rollout of an upgraded version of a web-based business information system are described. URLs associated with client requests remain the same even where the target subscriber accounts have been upgraded. Client requests for both upgraded and non-upgraded accounts are received by a common set of web servers. Client requests representing external entry points are trapped, and the receiving web server accesses a login router database to determine whether the target subscriber account is upgraded or non-upgraded, and then transfers the request to an appropriately-versioned application server. Application server sets are mapped to database sets according to system version, allowing the upgraded system database schema to be substantially different than the non-upgraded database schema. An early adopter program business method leveraging the abilities of such web-based business information system is also described. Applications to environments other than phased rollout are described, such as URL-agnostic differentiation and routing of client requests according to class-of-service of the target subscribing account.

Simultaneous maintenance of multiple versions of a web-based business information system

Phased rollout of version upgrades in web-based business information systems

Growing community of inventors

Boulder, CO, United States of America

Theodore Ray Rice