Scalable Event-Based Notifications

• US 20160323138A1
• Filed: 09/23/2015
• Published: 11/03/2016
• Est. Priority Date: 04/28/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Wun, Alex, Modi, Vipul A., Xun, Lu, Mohsin, Mansoor
• Granted Patent: US 10,069,941 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0695 the faulty arrangement being the maintenance, administration or management system
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Embodiments are directed to a cluster of nodes configured to run one or more services. A gateway on each node is configured to provide communication between the node and clients. The gateways manage filters designated by the clients, wherein the filters are named based upon a naming format used to name the services. The gateways receive configuration updates broadcast by a failover manager. The configuration updates comprise service endpoint changes for services running on the nodes. The gateways provide notifications to clients when a filter name matches at least a portion of a service name in a configuration update. The configuration updates identify a configuration version, and the gateways may provide notifications with endpoint information from more than one configuration update version. Notifications may be configured to be sent only when the endpoint for a primary replica of a service has changed.

Claims

1. A system, comprising:

a plurality of nodes configured to run one or more services, each of the nodes comprising a gateway configured to provide communication between the node and clients;

the gateways configured to manage filters designated by the clients, the filters named based upon a naming format used to name the services, wherein the gateways are further configured to receive service configuration updates comprising service endpoint changes and to provide notifications to clients when a filter name matches at least a portion of a service name in a configuration update.

2. The system of claim 1, further comprising:

a failover manager configured to manage service deployment on the plurality of nodes, the failover manager generating the configuration updates.

3. The system of claim 2, wherein the plurality of nodes are managed as a cluster in a distributed computing system.

4. The system of claim 1, wherein the configuration updates identify a configuration version, and wherein the gateways are further configured to provide notifications comprising endpoint information from more than one configuration update version.

5. The system of claim 1, wherein a filter is configured to match a prefix of a service name or configured to match an entire service name.

6. The system of claim 1, wherein the gateways provide notifications to clients only when the endpoint for a primary replica of a service has changed.

7. The system of claim 1, wherein the gateways are further configured to maintain a cache of received service configuration updates and to provide notifications to reconnected clients when the filter name matches at least a portion of a service name in the cache.

8. A computer-implemented method, comprising:

receiving, at a gateway on a node in a distributed computing system, a broadcast comprising service names and endpoints for the named services; and

generating a client notification when a client filter name matches a portion of a service name in the broadcast, the client notification comprising at least the endpoint for the matched service name.

9. The computer-implemented method of claim 8, further comprising:

receiving, at the gateway, a filter configuration from a client, the filter configuration comprising the filter name and a set of filter flags.

10. The computer-implemented method of claim 9, wherein the filter flags indicate whether a filter should be matched to an exact service name or to a prefix of a service name.

11. The computer-implemented method of claim 9, wherein the filter flags indicate that a client notification should be generated only when a filter name matches a service name for a primary replica of a service.

12. The computer-implemented method of claim 8, further comprising:

receiving a configuration update version in the broadcast; and

maintaining a record of configuration update versions associated with the client notifications sent to a client.

13. The computer-implemented method of claim 8, further comprising:

receiving the filter configuration from a reconnecting client;

comparing the filter name to a cache of configuration updates; and

generating the client notification when the client filter name matches a portion of a service name stored in a cached configuration update.

14. The computer-implemented method of claim 13, wherein the client notification comprises a version range identifying the configuration update versions associated with the client notification.

15. The computer-implemented method of claim 13, wherein the client notification comprise endpoints updated in both a current broadcast and in the cached configuration update.

16. The computer-implemented method of claim 8, further comprising:

receiving a synchronization request from a client, the synchronization request comprising a list of services the client considers active; and

in response to the synchronization request, generating a list of deleted services from the list of services the client considers active.

17. A computing node in a distributed computing system, comprising:

a gateway configured to provide communication between the node and clients;

a list of filters stored on the gateway, the filters designated by the clients and named using a naming format associated with services running on the distributed computing system;

the gateway configured to receive configuration updates from a failover manager on the distributed computing system, the configuration updates comprising endpoint changes for services running on the distributed computing system, and the gateway further configured to generate a client notification when a filter name matches a portion of a service name in a configuration update, the client notification comprising at least the endpoint for the matched service name.

18. The computing node of claim 17, wherein the configuration updates identify a configuration version, and wherein the gateway is further configured to provide notifications comprising endpoint information from more than one configuration update version.

19. The computing node of claim 17, wherein the filters are selectively configured by the clients to match the filter name to either a prefix of a service name or an entire service name.

20. The computing node of claim 17, wherein the gateway is further configured to maintain a cache of received configuration updates and to provide notifications to reconnected clients when a reconnected client'"'"'s filter name matches at least a portion of a service name in the cache.