Abstract: A loyalty switch for examining loyalty messages and routing the loyalty messages to one or more loyalty hosts and examining responses and routing the responses back to stores. Such a switch has configurable number of selector handlers pool, and the switch accepts a connection from stores and reads loyalty host information from master data to establish the connection with a loyalty host and to route messages. Each selector handler in the switch has multiple store objects that contain a routing map and connection information from companies' sites and the loyalty host.

Abstract: A surgical light including a light housing having at least one light source therein and a handle assembly extending from the light housing, with the handle assembly including a knob and a cover. The handle assembly is rotatably connected to the light housing. The cover covers the knob. Engaging the cover in a first mode and rotating the knob alters a first characteristic of light emitted from the at least one light source. Engaging the cover in a second mode and rotating the knob alters a second characteristic of light emitted from the at least one light source.

Abstract: A hybrid entity recognition system and accompanying method identify composite entities based on machine learning. An input sentence is received and is preprocessed to remove extraneous information, perform spelling correction, and perform grammar correction to generate a cleaned input sentence. A POS tagger tags parts of speech of the cleaned input sentence. A rules based entity recognizer module identifies first level entities in the cleaned input sentence. The cleaned input sentence is converted and translated into numeric vectors. Basic and composite entities are extracted from the cleaned input sentence using the numeric vectors.

Abstract: A loyalty switch for examining loyalty messages and routing the loyalty messages to one or more loyalty hosts and examining responses and routing the responses back to stores. Such a switch has configurable number of selector handlers pool, and the switch accepts a connection from stores and reads loyalty host information from master data to establish the connection with a loyalty host and to route messages. Each selector handler in the switch has multiple store objects that contain a routing map and connection information from companies’ sites and the loyalty host.

Abstract: A loyalty switch for examining loyalty messages and routing the loyalty messages to one or more loyalty hosts and examining responses and routing the responses back to stores. Such a switch has configurable number of selector handlers pool, and the switch accepts a connection from stores and reads loyalty host information from master data to establish the connection with a loyalty host and to route messages. Each selector handler in the switch has multiple store objects that contain a routing map and connection information from companies' sites and the loyalty host.

Abstract: A hybrid entity recognition system and accompanying method identify composite entities based on machine learning. An input sentence is received and is preprocessed to remove extraneous information, perform spelling correction, and perform grammar correction to generate a cleaned input sentence. A POS tagger tags parts of speech of the cleaned input sentence. A rules based entity recognizer module identifies first level entities in the cleaned input sentence. The cleaned input sentence is converted and translated into numeric vectors. Basic and composite entities are extracted from the cleaned input sentence using the numeric vectors.

Abstract: A loyalty switch for examining loyalty messages and routing the loyalty messages to one or more loyalty hosts and examining responses and routing the responses back to stores. Such a switch has configurable number of selector handlers pool, and the switch accepts a connection from stores and reads loyalty host information from master data to establish the connection with a loyalty host and to route messages. Each selector handler in the switch has multiple store objects that contain a routing map and connection information from companies' sites and the loyalty host.

Abstract: A loyalty switch for examining loyalty messages and routing the loyalty messages to one or more loyalty hosts and examining responses and routing the responses back to stores. Such a switch has configurable number of selector handlers pool, and the switch accepts a connection from stores and reads loyalty host information from master data to establish the connection with a loyalty host and to route messages. Each selector handler in the switch has multiple store objects that contain a routing map and connection information from companies' sites and the loyalty host.

Abstract: A loyalty switch for examining loyalty messages and routing the loyalty messages to one or more loyalty hosts and examining responses and routing the responses back to stores. Such a switch has configurable number of selector handlers pool, and the switch accepts a connection from stores and reads loyalty host information from master data to establish the connection with a loyalty host and to route messages. Each selector handler in the switch has multiple store objects that contain a routing map and connection information from companies' sites and the loyalty host.

Abstract: A system and method for hybrid entity recognition are disclosed. According to one embodiment, a computer-implemented process, comprises receiving an input sentence. The input sentence is preprocessed to remove extraneous information, perform spelling correction, and perform grammar correction to generate a cleaned input sentence. A POS tagger, tags parts of speech of the cleaned input sentence. A rules based entity recognizer module identifies first level entities in the cleaned input sentence. The cleaned input sentence is converted and translated into numeric vectors. Basic and composite entities are extracted from the cleaned input sentence using the numeric vectors.

Abstract: The disclosure is related to a shard manager that manages assignment of shards (data partitions) to application servers. An application service (“app service”) provides a specific service to clients and can be executing on multiple application servers. The dataset managed by the app service can be divided into multiple shards and the shards can be assigned to different app servers. The shard manager can manage the assignment of shards to different app servers based on an assignment policy. The shard assignments can be published to a configuration service. A client can request the configuration service to provide identification information of the app server to which a particular shard the client intends to access is assigned. The shard manager can also provide dynamic load balancing solutions. The shard manager can poll the app servers in runtime to determine the load information and per-shard resource usage, and balance the load by reassigning the shards accordingly.

Abstract: The disclosure is directed to a failover mechanism for failing over an application service, e.g., a messaging service, from servers in a first region to servers in a second region. Data is stored as shards in which each shard contains data associated with a subset of the users. Data access requests are served by a primary region of the shard. A global shard manager manages failing over the application service from a current primary region to a secondary region of the shard. A leader service in the application service replicates data associated with the application service from the primary to the secondary region, and ensures that the state of various other services of the application service in the secondary region is consistent. The leader service confirms that there is no replication lag between the primary and secondary regions and fails over the application service to the secondary region.

Abstract: The disclosure is directed to a failover mechanism for failing over an application service, e.g., a messaging service, from servers in a first region to servers in a second region. Data is stored as shards in which each shard contains data associated with a subset of the users. Data access requests are served by a primary region of the shard. A global shard manager manages failing over the application service from a current primary region of a shard to a secondary region of the shard. The current primary determines whether a criterion for failing over, e.g., a replication lag between the primary and the secondary regions is within a threshold, and if it is within the threshold, the failover process waits until the lag is zero. After the replication lag is zero, the application service is failed over to the second region, which then becomes the primary for the shard.

Abstract: The disclosure is related to a shard manager that manages assignment of shards (data partitions) to application servers. An application service (“app service”) provides a specific service to clients and can be executing on multiple application servers. The dataset managed by the app service can be divided into multiple shards and the shards can be assigned to different app servers. The shard manager can manage the assignment of shards to different app servers based on an assignment policy. The shard assignments can be published to a configuration service. A client can request the configuration service to provide identification information of the app server to which a particular shard the client intends to access is assigned. The shard manager can also provide dynamic load balancing solutions. The shard manager can poll the app servers in runtime to determine the load information and per-shard resource usage, and balance the load by reassigning the shards accordingly.

Abstract: Systems and methods provide automated provisioning of load balancing. In one implementation, a computer-implemented method configures an access point. A request to create the access point may be received and data for the access point may be stored in a data store. The method may invoke a workflow engine. The workflow engine may assign the access point to a load balancer, configure the load balancer, assign a network address to the load balancer, and publish the network address for a plurality of clients.