DYNAMIC MESSAGE QUEUES FOR A MICROSERVICE BASED CLOUD SERVICE

• US 20190089809A1
• Filed: 09/15/2017
• Published: 03/21/2019
• Est. Priority Date: 09/15/2017
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: THEEBAPRAKASAM, Arun, BALU, Balakumar, SHARMA, Himanshu
• Granted Patent: US 10,348,858 B2
• Time in Patent Office: Days
• CPC Class Codes: G05B 2219/33149 Publisher subscriber, publisher, master broadcasts data to slaves, subscriber
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 11/3065 Monitoring arrangements determined by the means or processing involved in reporting the monitored data error or fault reporting or logging G06F11/0766
• CPC Class Codes: G06F 11/3082 the data filtering being achieved by aggregating or compressing the monitored data
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 2009/45579 I/O management, e.g. providing access to device drivers or storage
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• 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 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2209/548 Queue
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 41/0273 using web services for network management, e.g. simple object access protocol [SOAP]
• CPC Class Codes: H04L 41/0604 using filtering, e.g. reduction of information by using priority, element types, position or time
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 51/52 : for supporting social networking services
• CPC Class Codes: H04L 63/0815 : providing single-sign-on or federations
• CPC Class Codes: H04L 63/1416 : Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/168 : above the transport layer
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1036 : Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
• CPC Class Codes: H04L 67/12 : specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/55 : Push-based network services
• CPC Class Codes: H04L 67/60 : Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

A cloud based identity management system that handles a plurality of published events that are published and consumed by microservices provides a dynamic queue that includes one or more active queues and one or more inactive queues. Embodiments create selectors for all of the active queues and the inactive queues and binds subscribers to each active queue. Embodiments dynamically cause at least one of the inactive queues to become one of the active queues when a number of published events increases.

Claims

1. A method of handling published events comprising:

providing a dynamic queue comprising one or more active queues and one or more inactive queues;

creating selectors for all of the active queues and the inactive queues;

binding subscribers to each active queue; and

dynamically causing at least one of the inactive queues to become one of the active queues when a number of published events increases.

2. The method of claim 1, wherein the events comprise Java Message Service (JMS) messages.

3. The method of claim 1, wherein the binding comprises dedicated database connections between the queues and the subscribers.

4. The method of claim 1, wherein the subscribers comprises a plurality of handlers.

5. The method of claim 4, wherein the plurality of handlers comprise an audit handler and a notify handler.

6. The method of claim 1, wherein the events are published by a publisher microservice, and the subscribers are implemented by a messaging microservice.

7. The method of claim 1, wherein the dynamic queue is implemented by a database comprising database tables.

8. A non-transitory computer readable medium having instructions stored thereon that, when executed by a processor, cause the processor to handle published events, the handle published events comprising:

providing a dynamic queue comprising one or more active queues and one or more inactive queues;

creating selectors for all of the active queues and the inactive queues;

binding subscribers to each active queue; and

dynamically causing at least one of the inactive queues to become one of the active queues when a number of published events increases.

9. The computer readable medium of claim 8, wherein the events comprise Java Message Service (JMS) messages.

10. The computer readable medium of claim 8, wherein the binding comprises dedicated database connections between the queues and the subscribers.

11. The computer readable medium of claim 8, wherein the subscribers comprises a plurality of handlers.

12. The computer readable medium of claim 11, wherein the plurality of handlers comprise an audit handler and a notify handler.

13. The computer readable medium of claim 8, wherein the events are published by a publisher microservice, and the subscribers are implemented by a messaging microservice.

14. The computer readable medium of claim 8, wherein the dynamic queue is implemented by a database comprising database tables.

15. A system for handling published events in providing cloud based identity and access management, comprising:

a plurality of tenants;

a dynamic queue comprising one or more active queues and one or more inactive queues;

a plurality of microservices; and

one or more processors that;

create selectors for all of the active queues and the inactive queues;

bind subscribers to each active queue; and

dynamically cause at least one of the inactive queues to become one of the active queues when a number of published events increases.

16. The system of claim 15, wherein the events comprise Java Message Service (JMS) messages.

17. The system of claim 15, wherein the binding comprises dedicated database connections between the queues and the subscribers.

18. The system of claim 15, wherein the subscribers comprises a plurality of handlers.

19. The system of claim 18, wherein the plurality of handlers comprise an audit handler and a notify handler.

20. The system of claim 15, wherein the events are published by a publisher microservice, and the subscribers are implemented by a messaging microservice.