Methods and systems for regulating database activity

• US 9,245,145 B2
• Filed: 03/07/2013
• Issued: 01/26/2016
• Est. Priority Date: 07/16/2012
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Wo, Zhaogang, Tejomurtula, Venkata Muralidhar, Patel, Maryann, Wong, Fang, Singh, Atul, Williams, Christopher, Nachnani, Pawan
• Primary Examiner(s): LE, DEBBIE M
• Application Number:
  US13/789,011
• Publication Number:
  US 20140019488A1
• Time in Patent Office: 1,055 Days
• Field of Search: 707/784
• US Class Current: 1/1
• CPC Class Codes: G06F 21/552 involving long-term monitoring or reporting
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/2135 Metering
• CPC Class Codes: H04L 63/1425 Traffic logging, e.g. anomaly detection

Abstract

Methods and systems are provided for regulating access to a database by a server. One exemplary method involves the server receiving one or more requests for an activity with respect to the database and determining an attempted usage for the activity over a monitoring period by a source of the requests. When the attempted usage exceeds an allowed usage of the activity for the monitoring period, the server provides a human verification test to the source and thereafter initiates the activity with respect to the database in response to receiving a satisfactory human verification response to the human verification test from the source.

Claims

1. A method of regulating access to a database by a server coupled to the database, the method comprising:

receiving, by the server, one or more requests for an activity;

determining, by the server, a number of requests for the activity received from a source of the one or more requests during a monitoring period, wherein determining the number of requests comprises;

generating a cache key based at least in part on the activity, the source, and the monitoring period; and

accessing a cache coupled to the server to obtain a counted number of requests for the activity associated with an entry in the cache matching the cache key;

automatically initiating, by the server, the activity with respect to the database when the number is less than an allowed number of requests for the activity for the monitoring period; and

providing, by the server to the source, a human verification test when the number of requests exceeds the allowed number of requests for the activity for the monitoring period, wherein the server continues servicing the one or more requests for the activity with respect to the database in response to receiving a satisfactory response to the human verification test from the source.

2. The method of claim 1, further comprising authenticating, by the server, the source prior to receiving the one or more requests.

3. The method of claim 2, wherein authenticating the source comprises verifying login information for a user of a client device coupled to the server via the network matches stored login information associated with the user in the database, the one or more requests being received from the client device.

4. The method of claim 1, wherein the number of requests comprise the counted number of requests for the activity received from the source during a preceding time interval equal to the monitoring period, wherein:

the server automatically initiates the activity with respect to the database when the counted number is less than an allowed number of requests for the activity for the monitoring period; and

the server provides the human verification test to the source when the counted number is greater than the allowed number of requests.

5. The method of claim 1, wherein generating the cache key comprises:

calculating a window value based on a current reference time for the server and the monitoring period; and

appending the window value to a first value indicative of the activity and a second value indicative of the source.

6. The method of claim 5, wherein calculating the window value comprises:

dividing the current reference time for the server by the monitoring period to obtain a quotient; and

performing a modulus operation on the quotient, wherein the window value comprises a residue of the modulus operation.

7. The method of claim 1, further comprising:

incrementing the counted number of requests; and

after incrementing the counted number;

providing, by the server, the human verification test to the source when the counted number exceeds an allowed number of requests for the activity for the monitoring period; and

initiating, by the server, the activity with respect to the database in response to receiving, from the source, the satisfactory response to the human verification test.

8. The method of claim 1, further comprising preventing the activity with respect to the database on behalf of the source in response to receiving an unsatisfactory response to the human verification test from the source when the number of requests exceeds the allowed number of requests.

9. The method of claim 8, wherein preventing the activity comprises:

calculating a time value indicative of when the source can resume initiating the activity with respect to the database based on a current reference time for the server; and

creating an entry in a cache coupled to the server, wherein the entry maintains an association between the source and the time value.

10. The method of claim 8, wherein preventing the activity comprises updating a database record associated with the source and maintained by the database to indicate the source has been prevented from initiating the activity.

11. The method of claim 1, further comprising:

receiving, by the server, a plurality of requests for the activity from a plurality of sources;

determining a confidence interval for a number of requests per source over the monitoring period based on the plurality of requests; and

determining an upper limit of the confidence interval as the allowed number of requests for the activity for the monitoring period.

12. The method of claim 11, the number of requests comprising the counted number of requests for the activity received from the source during a preceding time interval equal to the monitoring period, wherein:

the server automatically initiates the activity with respect to the database when the counted number is less than the allowed number of requests; and

the server provides the human verification test to the source when the counted number is greater than the allowed number of requests.

13. The method of claim 1, further comprising determining, by the server, a second number of requests for the activity received from the source of the one or more requests during a second monitoring period, the second monitoring period being different from the first monitoring period, wherein:

the server provides the human verification test to the source when the number of requests exceeds the allowed number of requests for the monitoring period or the second number of requests exceeds a second allowed number of requests for the second monitoring period; and

the server initiates the activity with respect to the database in response to receiving the satisfactory response.

14. A computing system comprising:

a database;

a server coupled to the database to receive, from a source via a network, one or more requests for an activity, determine a counted number of requests by the source for the activity over a preceding time interval equal to a monitoring period exceeds an allowed number of requests for the activity for the monitoring period, and when the counted number of requests exceeds the allowed number of requests for the activity for the monitoring period, initiate the activity with respect to the database in response to receiving human verification from the source; and

a cache coupled to the server via the network, the server generating a cache key for an entry in the cache based at least in part on the activity, the source, and the monitoring period and the server accessing the cache utilizing the cache key to obtain the counted number of requests associated with the entry, the entry maintaining an association between the source and the counted number of requests for the activity by the source over the preceding time interval equal to the monitoring period.

15. The computing system of claim 14, wherein the allowed number of requests comprises an upper limit of a confidence interval for a number of requests per source over the monitoring period determined based on a plurality of requests received from a plurality of sources.

16. The computing system of claim 14, wherein the source comprises a user of a client device coupled to the network, the user being authenticated based on login information received from the client device prior to receiving the one or more requests.

17. A computer-readable medium comprising computer-executable instructions that, when executed by a processing system, cause the processing system to:

determine a number of requests for an activity with respect to a database received from a source during a monitoring period in response to receiving one or more requests for the activity from the source by;

generating a cache key based at least in part on the activity, the source, and the monitoring period; and

accessing a cache to obtain a counted number of requests for the activity associated with an entry in the cache matching the cache key;

automatically initiate the activity with respect to the database when the number is less than an allowed number of requests for the activity for the monitoring period; and

initiate the activity with respect to the database in response to receiving human verification from the source when the number of request exceeds the allowed number of requests for the activity for the monitoring period.

18. The computer-readable medium of claim 17, wherein:

the source comprises a previously authenticated user of a client device coupled to the processing system via a network; and

the allowed number of requests comprises an upper limit of a confidence interval for a number of requests per source over the monitoring period, the confidence interval being determined based on a plurality of requests received by the processing system via the network from a plurality of sources.