A cloud computing platform contains a structured storage subsystem the provides scalable queues. The cloud computing platform monitors message throughput for the scalable queues and automatically increases or decreases subqueues that provide the operational functionality for each scalable queue. A visibility start time and cloud computing platform time are maintained for each message to provide an approximate first-in-first-out order for messages within each subqueue. A message in a subqueue may be available for processing when the current cloud computing time is greater than the visibility start of the message.
Legal claims defining the scope of protection, as filed with the USPTO.
1. A computer-implemented method to manage a scalable queue, the method performed in a cloud computing platform and comprising: receiving messages to add to a scalable queue, wherein the scalable queue is a virtual queue comprising the plurality of subqueues, wherein the messages are added to the plurality of subqueues, and wherein each message comprises a visibility start time that indicates a processing order for messages in the plurality of subqueues; ordering the messages in each subqueue based on the visibility start time, wherein the visibility start time indicates when each message is available for dequeing; and obtaining one or more of the messages based on comparing a time maintained by the cloud computing platform to the visibility start time of the one or more messages, wherein one or more messages are obtained when the visibility start time of the one or more messages is earlier than the time maintained by the cloud computing platform.
2. The computer-implemented method of claim 1 , wherein adding new messages to a subqueue sets the visibility start times to a time maintained by one or more table servers operating within the cloud computing platform.
3. The computer-implemented method of claim 1 , wherein dequeing a message updates the visibility start time of the obtained message to the current time maintained by the cloud computing platform plus a threshold time.
4. The computer-implemented method of claim 1 , wherein dequeing a message does not update the visibility start time when a cloud application deletes the message.
5. The computer-implemented method of claim 3 , wherein one or more messages are not obtained when the visibility start time of the one or more messages is later than the time maintained by the cloud computing platform.
6. The computer-implemented method of claim 3 , further comprising sorting the messages in each subqueue based on priority.
7. The computer-implemented method of claim 3 , wherein obtaining one or more of the messages based on a time maintained by the cloud computing platform further includes obtaining messages having visibility start time less than the time maintained by the one or more table servers.
8. One or more tangible computer-readable media storing instructions to perform a method to manage a scalable queue, the method performed in a cloud computing platform and comprising: receiving messages to add to a scalable queue, wherein the scalable queue is a virtual queue comprising a plurality of subqueues, wherein the messages are added to the plurality of subqueues to provide automatic scaling based on a throughput load on the scalable queue, and wherein each message comprises a visibility start time that indicates a processing order for messages in the plurality of subqueues; ordering the messages in each subqueue based on a visibility start time, wherein the visibility start time indicates when each message is available for dequeueing; and obtaining one or more of the messages based on comparing a time maintained by the cloud computing platform to the visibility start time of the one or more messages.
9. The media of claim 8 , wherein adding new messages to a subqueue sets the visibility start times to a time maintained by one or more table servers operating within the cloud computing platform.
10. The media of claim 8 , wherein dequeing a message updates the visibility start time of the obtained message to the current time maintained by the cloud computing platform plus a threshold time.
11. The media of claim 8 , wherein dequeing a message does not update the visibility start time when a cloud application deletes the message.
12. The computer-implemented method of claim 10 , wherein one or more messages are not obtained when the visibility start time of the one or more messages is later than the time maintained by the cloud computing platform.
13. The media of claim 10 , further comprising sorting the messages in each subqueue based on priority.
14. The media of claim 10 , wherein obtaining one or more of the messages based on a time maintained by the cloud computing platform further includes obtaining messages having visibility start time less than the time maintained by the one or more table servers.
15. A system for managing a scalable queue in a cloud computing platform, the system comprising: a front end server for: receiving messages to add to a scalable queue, wherein the messages are added to a plurality of subqueues, wherein each message comprises a visibility start time that indicates a processing order for messages in the plurality of subqueues; ordering the messages in each subqueue based on the visibility start time, wherein the visibility start time indicates when each message is available for dequeueing; and obtaining one or more of the messages based on comparing a time maintained by the cloud computing platform to the visibility start time of the one or more messages.
16. The system of claim 15 , wherein one or more table servers are operated within the cloud computing platform, the one or more table servers configured for maintaining a time on which visibility start times are set to when adding new messages to a subqueue.
17. The system of claim 15 , wherein one or more table servers are configured to maintain a current time to which a threshold time is added, in order to update the visibility start time of the one or more obtained messages when the one or more obtained messages is dequeued.
18. The system of claim 15 , wherein one or more table servers are configured to maintain a visibility start time that is not updated when a cloud application deletes the message.
19. The system of claim 17 , wherein the one or more table servers are further configured to store the messages that are sorted in each subqueue based on priority.
20. The system of claim 17 , wherein the one or more table servers are further configured to maintain a time, wherein messages having a visibility start time less than the time maintained by the one or more table servers are obtained.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
May 15, 2012
July 1, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.