Microsoft Technology Licensing, LLC

Vinod Shanbhag

Kartik Paramasivam

Jayteerth Narasingrao Katti

Ramasubramaniam Poornalingam

Satish Kumar Musukula

Zengzhong Li

Bi Xue

Vikas Sabharwal

Vivek Bhaskaran Iyer

Dharma Kiritkumar Shukla

Aditya G Bhandarkar

Girish Mittur Venkataramanappa

Yann Christensen

Amol Kulkarni

Elio Damaggio

Chandra Prasad

Sumit Mohanty

Govindaraj Ramanathan

Stuart J Langley

Andreas Ulbrich

Sebastian Bengochea

Juan D Ferré

Mandyam Kishore

Pan Wang

Brent Schmaltz

Jayteerth Katti

Ramasubramanian Poornalingam

Systems, apparatuses, services, platforms, and methods are discussed herein that provide user search services to a communication platform. An example user search service receives a query indicted by a user to find users of a communication platform associated with one or more search terms. The example user search service also presents to the user a search result view comprising resultant users on the communication platform, where the search result view includes one or more graphical annotations in association with ones of the resultant users that indicate a quantity of common users on the communication platform between the user and the ones of the resultant users.

Search prioritization interfaces for communication platform users

Systems, apparatuses, services, platforms, and methods are discussed herein that provide user search services to a communication platform. An example user search service receives a user query to find users of the communication platform associated with one or more search terms, performs a graph search process based at least on the one or more search terms to identify a first set of users related to the user through at least one common user, and performs an indexed search process to identify a second set of users associated with the one or more search terms. The user search service then presents to the user a result view comprising the first set of users prioritized over the second set of users.

Search prioritization among users in communication platforms

Embodiments are directed to registering a device to receive notifications. In one scenario, a computer system receives a notification registration request from a computing device. The computer system generates a registration secret which includes identification information that uniquely identifies the computing device, and sends the generated registration secret including the information that uniquely identifies the computing device to a notification service. The computer system receives a hash value from the computing device, where the hash value is generated based on the identification information of the generated registration secret. The computer system computes another hash value based on the identification information of the received registration secret to determine whether the second hash value matches the first hash value, and upon determining that the second hash value matches the first hash value, the computer system registers the computing device to receive notifications from the notification service.

Device verification prior to registration

The present invention extends to methods, systems, and computer program products for automatically re-starting services. Embodiments of the invention can be used to re-start a service when it is determined that the service stopped during the processing pending work. A container manager durably tracks a service's status (busy/idle and alive/dead) and tracks transitions between statuses. Accordingly, when a busy service is deemed dead (due to any event), the container manager can automatically re-start the service. Upon re-start the service can check for pending work and start executing its pending work.

Automatically re-starting services

A container service is capable of hosting large numbers of middleware components for multiple tenants. A central container manager controls a plurality of compute nodes. The central container manager receives middleware components from external devices or services and assigns the components to containers on one or more designated compute nodes. Each compute node has a container management agent and one or more containers. The container management agents activate and manage the appropriate number of containers to run the assigned middleware components. The container management agent assigns each container on its compute node a limited set of privileges to control access to shared resources. The central container manager and each node's container management agent monitor container load levels and dynamically adjust the placement of the middleware components to maintain balanced operation. The compute nodes are grouped into clusters based upon the type of middleware components hosted on each compute node.

Multi-tenant, high-density container service for hosting stateful and stateless middleware components

The present invention extends to methods, systems, and computer program products for load balancing for services. Embodiments of the invention facilitate load balancing between instances of a service based on affinitization of messages, based on content of the message. For example, messages in the same session can be dispatched to the same service instance. A sequence or series of related messages associated with long running and/or stateful services are more likely to be dispatched to the same instance of the service. Thus, if the service instance has persisted client state, there is an increased likely of utilizing the persisted client state and not having another service instance recreate the client state.

Load balancing for services

Growing community of inventors

Redmond, WA, United States of America

Vinod Shanbhag