Microsoft Technology Licensing, LLC

Marios Zikos

Parveen Kumar Patel

Deepak Bansal

Ashwin Narasimha Murthy

David Allen Dion

Vladimir Petter

Vyacheslav Kuznetsov

Volodymyr Ivanov

Narasimhan Agrahara Venkataramaiah

Eric Joseph Winner

Nelamangala Krishnaswamy Srinivas

Naveen Reddy Karri

Narayanan Annamalai

HongYu Wu

Yagya Narayanan Sethuraman

Embodiments are directed to routing requests with different protocols to the same destination. In one scenario, a computer system receives a request that uses a specified protocol. The request includes a request source identifier and a request destination identifier. The computer system identifies, based on both the request source identifier and the request destination identifier, a destination to send the request to and generates a routing entry for the request that indicates which destination the first request was sent to. The computer system receives another request that uses a different protocol. This request includes a request source identifier and a request destination identifier of its own. The computer system determines that the request source identifier and request destination identifier of the subsequent request match those of the generated routing entry, and routes the subsequent request to the destination indicated in the routing entry.

Routing requests with varied protocols to the same endpoint within a cluster

The present invention extends to methods, systems, and computer program products for synchronizing state among load balancer components. Embodiments of the invention include load balancers using a consistent hashing algorithm to decide how new connections should be load balanced. Use of consistent hashing algorithm permits load balancers to work in a stateless manner in steady state. Load balancers start keeping flow state information (destination address for a given flow) about incoming packets when it is needed, i.e. such as, for example, when a change in destination host configuration is detected. State information is shared across load balancers in a deterministic way, which allows knowing which load balancer is authoritative (e.g., is the owner) for a given flow. Each load balancer can reach the authoritative load balancer to learn about a flow that cannot be determined locally.

Synchronizing state among load balancer components

When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Load balancing for single-address tenants

A load balancer that is able to detect and mitigate a Denial of Service (DOS) attack. The load balancer is placed in the flow path of network data packets that are destined for one or more tenant addresses. The load balancer analyzes performance parameters regarding the network data packets that are destined for the one or more tenant addresses and are received at the load balancer. The performance parameters describe network data packet flow to the tenant addresses. The load balancer detects, based on the analysis of the performance parameters, that one or more of the tenant addresses are being subjected to a DOS attack. The load balancer performs a mitigation operation to isolate the one or more tenant addresses being subjected to the DOS attack.

DOS detection and mitigation in a load balancer

A system and method for converting a target computing device to a virtual machine are provided. A conversion event is detected to initiate a conversion of a target computing device to a virtual machine. An assessment of the physical and software assets of a target computing device are obtained. A data image of the target computing device is deployed on an instance of a virtual machine. The virtual machine adjusted to correspond to the physical and software assets of the target computing device.

System and method for converting a target computing device to a virtual machine in response to a detected event

Growing community of inventors

Alexandroupolis, Greece

Marios Zikos