Microsoft Technology Licensing, LLC

Jayteerth Narasingrao Katti

Kartik Paramasivam

Muralidhar Krishnaprasad

Santosh Chandwani

Nicholas Alexander Allen

Kenneth David Wolf

Justin David Brown

Stephen Jared Maine

Stefan R Batres

Anil Kumar Nori

Vinod Shanbhag

Ramasubramaniam Poornalingam

Edmund S V Pinto

Victor Boctor

Shivakumar Seetharaman

Jaroslav Dunajsky

Manu Srivastava

Govindaraj Ramanathan

Pramod Gurunath

Lei Yu

Stuart J Langley

Darrell Brunsch

Pan Wang

Aleksandar Boljanac

Stuart John Langley

Elvin Morales

Brent Schmaltz

Nimeesh Patel

Alexsandar Bojanac

A connector surfaces a configuration user experience that allows a user to select notifications that a user wishes to receive from a service. The user's e-mail system has a URL endpoint identifier, and the service sends the selected notifications to the URL endpoint. The notifications are integrated into the user's inbox, as e-mail messages.

Service integration into electronic mail inbox

The automatic provisioning of a connection between a public cloud and an on-premises resource in a private network. This allows a connection to be more easily made when an application in the public cloud is to access that on-premises resource in the private network. The automatic provisioning is initiated upon determining that an application running in the public cloud is to access the on-premises resource. The provisioning occurs by identifying a bridging infrastructure that provides access to the on-premises resource. Credentials are then accessed for later use in connecting to the bridging infrastructure. Application-specific credentials are securely provided to the application. The application-specific credentials are usable by an agent on the public cloud to connect to the identified bridging infrastructure. A configuration packages is then created that includes resource-specific credentials, the identity of the on-premises resource and an executable.

Connecting public cloud with private network resources

The automatic establishing of the connection between the public cloud and the on-premises resource. First, the bridging infrastructure is automatic accessed. The bridging infrastructure is configured to interact with a user system within the private network using a first control. For instance, it is this first control that may be represented as an executable within the configuration package used in provisioning the connection. A second control is provided to the application running in the public cloud. The second control is structured such that the at least one application may be used to securely connect via the bridging infrastructure with an on-premises resource of the private network.

Connecting public cloud applications with private network resources

A messaging entity configured in a memory of first node of a plurality communicatively coupled nodes is disclosed. The nodes are included in a distributed computing system. The messaging entity is configured to operate as a secondary messaging entity in a messaging server for the plurality communicatively coupled nodes. The messaging entity is communicatively couple to a primary messaging entity configured in a memory of a second node of the plurality of nodes. The primary messaging entity is configured to store a message; store a copy of the message.

Consistent messaging with replication

Network and storage calls are reduced by batching messages. Messages are collected from a client and sent to the gateway or backend application in one round trip. Alternatively, the messages are collected for different entities, and the batched messages are durably stored. Related messages, which may have the same sessionID, are grouped into a logical unit or session. This session may be locked to a single message consumer. A session may be associated with an application processing state as an atomic unit of work while other operations are performed on the messages in the session. Acknowledgements are accumulated by a broker on a message server, but the messages are not immediately deleted. Instead, multiple messages in a selected range are periodically truncated from a message store in a single operation. Expired messages for active sessions are proactive cleaned up to prevent sessions from reaching a quota or limit.

Message queue behavior optimizations

Processing messages. Messages are processed based on a characteristic derived from information in messages, metadata about messages, or other information external to messages. Values for one or more pieces of information are received. At least one of the values for one or more pieces of information is associated with a first message. Queries are received. The queries specify one or more of the pieces of information. At least a portion of the plurality of values for the one or more pieces of information is processed in conjunction with the one or more queries to create one or more normalized characteristics for the first message. The one or more normalized characteristics for the first message are in a same format irrespective of the format of the pieces of information. The first message, and/or other messages, is processed based on at least one of the one or more normalized characteristics.

Query-oriented message characterization

A messaging entity configured in a memory of first node of a plurality communicatively coupled nodes is disclosed. The nodes are included in a distributed computing system. The messaging entity is configured to operate as a secondary messaging entity in a messaging server for the plurality communicatively coupled nodes. The messaging entity is communicatively couple to a primary messaging entity configured in a memory of a second node of the plurality of nodes. The primary messaging entity is configured to store a message; store a copy of the message. Also, the messaging entity is configured to be promoted to a new primary messaging entity in the event of failure of the primary messaging entity.

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

Messages are processed based on a characteristic derived from information in messages, metadata about messages, or other information external to messages. Values for one or more pieces of information are received. At least one of the values for one or more pieces of information is associated with a first message. Queries are received. The queries specify one or more of the pieces of information. At least a portion of the plurality of values for the one or more pieces of information is processed in conjunction with the one or more queries to create one or more normalized characteristics for the first message. The one or more normalized characteristics for the first message are in a same format irrespective of the format of the pieces of information. The first message, and/or other messages, is processed based on at least one of the one or more normalized characteristics.

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.

Growing community of inventors

Redmond, WA, United States of America

Jayteerth Narasingrao Katti