Intuit, Inc.

Laurent R Benchimol

Hung T Nguyen

Jason Michael Webb

Venkatesan Murugesan

Alexey Povkh

Karim Lakhani

Samy Mohamed Ismail Mohamed

Sarika N Kale

Miroslav Svetoslavov Boussarov

Anil Kumar Attuluri

Viraj Raghunath Kulkarni

Joseph Seng Peacock

Gao Pan

A computing system receives, from a client device, a first request for access to a single page application associated with the computing system. A gateway of the computing system intercepts the first request before it reaches a shell service associated with the single page application. The gateway sends a second request for the single page application to the shell service. Based on the single page application request, the gateway determines that the shell service is experiencing a failure. Responsive to determining that the shell service is experiencing a failure, the gateway retrieves, from a content delivery network, a uniform resource locator (URL) associated with a time-lapse hypertext markup language (HTML) of the single page application. The gateway redirects the client device to the time-lapse HTML of the single page application using the URL.

High resiliency content delivery network backup mechanism for micro frontend web applications

API gateway log data of HTTP response information is collected and aggregated for each API service. The log data is streamed and formed into a feature vector. A model training module trains a neural network model based on the feature vector and model metadata. The model training module also retrains the neural network model based on a new feature vector. Neural network model artifacts are stored and used to detect anomalous patterns and generate alerts of the detection.

System and method for detecting anomalies utilizing a plurality of neural network models

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

Laurent R Benchimol