Intuit, Inc.

Anil Kumar Attuluri

Jason Michael Webb

Dhivya Arumugam

Sagar Shukla

A Sushanth Kamath

Rajendra Jayendra Gosavi

Nandan B N

Laurent R Benchimol

Karim Lakhani

Gokul Sarangapani

Viraj Raghunath Kulkarni

Venkata Krishna Murthy Vadrevu

Akash Jain

Gourav Yadav

Joseph Seng Peacock

Madhavan Narayanan

Mohamed Samy Ismail

Sushanth Kamath A

A method in a client backoff filter. The method includes receiving, from a server, a backoff data packet having backoff metadata. The method also includes saving the backoff metadata in a cache local to the client backoff filter. The method also includes receiving a subsequent request for service. The method also includes checking whether an attribute of the subsequent request for service matches the backoff metadata in the cache. The method also includes performing, responsive to checking, an action including at least one of the group including: blocking, responsive to the attribute matching the backoff metadata in the cache, transmission of the subsequent request for service to a server, and transmitting, responsive to the attribute failing to match the backoff metadata in the cache, the subsequent request for service to the server.

Client side backoff filter for rate limiting

A method including receiving, from a server, a backoff data packet including first information and second information. The first information includes a backoff command to cease transmitting at least some requests to a service executing on the server, and The second information includes metadata. The method also includes adding the backoff data packet to cached data stored in a cache. The method also includes receiving, from a client, a request data packet including a request for the service. The method also includes comparing request information, associated with the request data packet, to the cached data, including at least comparing the request information to the metadata. The method also includes blocking, responsive to a match between the request information and the cached data, the request data packet from being transmitted to the service.

Systems and methods for throttling requests to web services are disclosed. A system is configured to receive, at a host, one or more requests during a first time period. Each request is for a web service hosted on a backend. The host is one of a plurality of hosts of an application programming interface (API) gateway to receive a plurality of requests for the web services. The system is further configured to: process at least a portion of the one or more requests for the one or more web services; count, by a local counter in a local cache of the host, the one or more requests received at the host during the first time period; compare a local count of the local counter to a local bucket size associated with the host; and provide an instruction to update a remote count of a remote counter based on the comparison.

Scalable throttling of requests to web services

A method may include obtaining a first dependency of a first calling service on a called service and a second dependency of a second calling service on the called service. The method may further include generating a first routing configuration for the first calling service that maps a name of the called service to an ingress point of a first cluster, generating a second routing configuration for the second calling service that maps the name of the called service to the ingress point of the first cluster, detecting a relocation of the called service to a second cluster, modifying the first routing configuration to map the name of the called service to an ingress point of the second cluster, and modifying the second routing configuration to map the name of the called service to a local name of the called service within a namespace of the second cluster.

Contextual routing configuration and service naming for multi-cluster service mesh

Growing community of inventors

San Diego, CA, United States of America

Anil Kumar Attuluri