Abstract: Systems and methods for providing targeted event notifications to subscribers are disclosed. In an example embodiment, events may be received from a publisher. The events may be categorized into a plurality of topics. The events may be distributed among brokers to process a topic selected from the plurality of topics based on the events. Further, it may be determined whether the topic exists in a list of topics handled by the brokers. Authentication credentials of the publisher may be validated, based on the determination. Based on the validation, queues of the events may be formed based on an order of receipt of the events. The events present in the queues may be filtered based on subscriptions of the events. For the fileted events, targeted even notifications may be forwarded to the subscribers.

Abstract: Systems and methods for filtering and routing event notifications to subscribers are disclosed. In an example embodiment, events from a publisher may be received. Each of the events may be associated with a topic, and the topic may be compared with topics present in broker metadata cache, based on one of prefixes and a fast lookup technique using a hash-table. Further, it may be determined whether the topic associated the events is present in the broker metadata cache based on comparison. Based upon determining, matching nodes for the events may be retrieved. Further, the events may be routed based on routing tables and availability of the matching nodes. Based on the routing, the events may be forwarded to the subscribers.

Abstract: Systems and methods for filtering and routing event notifications to subscribers are disclosed. In an example embodiment, events from a publisher may be received. Each of the events may be associated with a topic, and the topic may be compared with topics present in broker metadata cache, based on one of prefixes and a fast lookup technique using a hash-table. Further, it may be determined whether the topic associated the events is present in the broker metadata cache based on comparison. Based upon determining, matching nodes for the events may be retrieved. Further, the events may be routed based on routing tables and availability of the matching nodes. Based on the routing, the events may be forwarded to the subscribers.

Abstract: Systems and methods for dispatching targeted event notifications to subscribers are disclosed. In an embodiment, the system includes a receiver to receive events from a publisher. The system further comprises a router in communication with the receiver to route the events. The system further comprises a director to forward the targeted event notifications to the subscribers based on the routing. The director receives a delivery status of the targeted event notification from the subscribers. The delivery status includes one of success in receiving the targeted event notification and failure in receiving the targeted event notification. The director receives an event notification with the delivery status as failure in receiving the targeted event notification. The director places the targeted event notification in a delayed queue indicative of events to be delivered after a predefined time. The director re-transmits the targeted event notification to the subscribers based on the delayed queue.

Abstract: Systems and methods for dispatching targeted event notifications to subscribers are disclosed. In an example embodiment, a notification indicating creation of an even subscription by a subscriber may be received. An event source may be invoked to enable publishing of events corresponding to an event topic associated with the event subscription. A response from the event source for publishing of the events may be received and targeted event notifications may be forwarded to the subscribers on receiving the response.

Abstract: Publishing events. A method includes a publisher sending a message comprising one or more events to a domain. The domain is a container comprising a group of domain topics. Each domain topic in the domain is relevant by subject matter to the one or more events by virtue of belonging to the container. The method further includes, at the domain determining the appropriate domain topics from the group of domain topics for each event in the one or more events. The method further includes identifying subscribers to the appropriate domain topics. The method further includes sending notifications to the subscribers of the domain topics of the one or more events.

Abstract: Systems and methods for providing targeted event notifications to subscribers are disclosed. In an example embodiment, events may be received from a publisher. The events may be categorized into a plurality of topics. The events may be distributed among brokers to process a topic selected from the plurality of topics based on the events. Further, it may be determined whether the topic exists in a list of topics handled by the brokers. Authentication credentials of the publisher may be validated, based on the determination. Based on the validation, queues of the events may be formed based on an order of receipt of the events. The events present in the queues may be filtered based on subscriptions of the events. For the fileted events, targeted even notifications may be forwarded to the subscribers.

Abstract: Systems and methods for providing targeted event notifications to subscribers are disclosed. In an example embodiment, events may be received from a publisher. The events may be categorized into a plurality of topics. The events may be distributed among brokers to process a topic selected from the plurality of topics based on the events. Further, it may be determined whether the topic exists in a list of topics handled by the brokers. Authentication credentials of the publisher may be validated, based on the determination. Based on the validation, queues of the events may be formed based on an order of receipt of the events. The events present in the queues may be filtered based on subscriptions of the events. For the fileted events, targeted even notifications may be forwarded to the subscribers.

Abstract: Publishing events. A method includes a publisher sending a message comprising one or more events to a domain. The domain is a container comprising a group of domain topics. Each domain topic in the domain is relevant by subject matter to the one or more events by virtue of belonging to the container. The method further includes, at the domain determining the appropriate domain topics from the group of domain topics for each event in the one or more events. The method further includes identifying subscribers to the appropriate domain topics. The method further includes sending notifications to the subscribers of the domain topics of the one or more events.

Abstract: Systems and methods for dispatching targeted event notifications to subscribers are disclosed. In an embodiment, the system includes a receiver to receive events from a publisher. The system further comprises a router in communication with the receiver to route the events. The system further comprises a director to forward the targeted event notifications to the subscribers based on the routing. The director receives a delivery status of the targeted event notification from the subscribers. The delivery status includes one of success in receiving the targeted event notification and failure in receiving the targeted event notification. The director receives an event notification with the delivery status as failure in receiving the targeted event notification. The director places the targeted event notification in a delayed queue indicative of events to be delivered after a predefined time. The director re-transmits the targeted event notification to the subscribers based on the delayed queue.

Abstract: Systems and methods for filtering and routing event notifications to subscribers are disclosed. In an example embodiment, events from a publisher may be received. Each of the events may be associated with a topic, and the topic may be compared with topics present in broker metadata cache, based on one of prefixes and a fast lookup technique using a hash-table. Further, it may be determined whether the topic associated the events is present in the broker metadata cache based on comparison. Based upon determining, matching nodes for the events may be retrieved. Further, the events may be routed based on routing tables and availability of the matching nodes. Based on the routing, the events may be forwarded to the subscribers.

Abstract: Systems and methods for providing targeted event notifications to subscribers are disclosed. In an example embodiment, events may be received from a publisher. The events may be categorized into a plurality of topics. The events may be distributed among brokers to process a topic selected from the plurality of topics based on the events. Further, it may be determined whether the topic exists in a list of topics handled by the brokers. Authentication credentials of the publisher may be validated, based on the determination. Based on the validation, queues of the events may be formed based on an order of receipt of the events. The events present in the queues may be filtered based on subscriptions of the events. For the fileted events, targeted even notifications may be forwarded to the subscribers.

Abstract: Aspects of the subject matter described herein relate migrating message for a messaging service. In aspects, a determination is made that messages need to be migrated based on a threshold being crossed. In response, an agent is instructed to migrate data associated with the messages to another location. The agent uses various factors to determine one or more queues to migrate. While a queue is being migrated, during a first portion of the migration, messages may be added to and removed from the queue as senders send new messages and receivers consume messages. During a second portion of the migration, the queue is frozen to disallow the queue to be used for receiving new messages and delivering queued messages. The migration may be orchestrated to attempt to achieve certain goals.

Abstract: Aspects of the subject matter described herein relate migrating message for a messaging service. In aspects, a determination is made that messages need to be migrated based on a threshold being crossed. In response, an agent is instructed to migrate data associated with the messages to another location. The agent uses various factors to determine one or more queues to migrate. While a queue is being migrated, during a first portion of the migration, messages may be added to and removed from the queue as senders send new messages and receivers consume messages. During a second portion of the migration, the queue is frozen to disallow the queue to be used for receiving new messages and delivering queued messages. The migration may be orchestrated to attempt to achieve certain goals.

Abstract: Aspects of the subject matter described herein relate migrating message for a messaging service. In aspects, a determination is made that messages need to be migrated based on a threshold being crossed. In response, an agent is instructed to migrate data associated with the messages to another location. The agent uses various factors to determine one or more queues to migrate. While a queue is being migrated, during a first portion of the migration, messages may be added to and removed from the queue as senders send new messages and receivers consume messages. During a second portion of the migration, the queue is frozen to disallow the queue to be used for receiving new messages and delivering queued messages. The migration may be orchestrated to attempt to achieve certain goals.

Abstract: Techniques are provided for scheduled and non-scheduled delivery of messages. A message directed to at least one consumer is received at a message entity. The message is determined to include a scheduled delivery time. The received message is stored in a scheduled sub-queue of the message entity. Activation metadata is retrieved and stored for any messages stored in the scheduled sub-queue that include a scheduled delivery time within a predetermined upcoming time period. If when the message is received, the scheduled delivery time of the message is within a current activation window, the activation metadata for the message may be extracted and stored immediately. The stored activation metadata is analyzed to determine a batch of messages in the scheduled sub-queue ready for delivery. The determined batch of messages is stored in an active sub-queue of the message entity, to be ready for delivery at the request of a consumer.

Abstract: Techniques are provided for scheduled and non-scheduled delivery of messages. A message directed to at least one consumer is received at a message entity. The message is determined to include a scheduled delivery time. The received message is stored in a scheduled sub-queue of the message entity. Activation metadata is retrieved and stored for any messages stored in the scheduled sub-queue that include a scheduled delivery time within a predetermined upcoming time period. If when the message is received, the scheduled delivery time of the message is within a current activation window, the activation metadata for the message may be extracted and stored immediately. The stored activation metadata is analyzed to determine a batch of messages in the scheduled sub-queue ready for delivery. The determined batch of messages is stored in an active sub-queue of the message entity, to be ready for delivery at the request of a consumer.

Abstract: Aspects of the subject matter described herein relate migrating message for a messaging service. In aspects, a determination is made that messages need to be migrated based on a threshold being crossed. In response, an agent is instructed to migrate data associated with the messages to another location. The agent uses various factors to determine one or more queues to migrate. While a queue is being migrated, during a first portion of the migration, messages may be added to and removed from the queue as senders send new messages and receivers consume messages. During a second portion of the migration, the queue is frozen to disallow the queue to be used for receiving new messages and delivering queued messages. The migration may be orchestrated to attempt to achieve certain goals.