The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.

The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.

Date of Patent:
Oct. 19, 2021

Filed:

Aug. 26, 2020
Applicant:

Software Ag, Darmstadt, DE;

Inventors:
Assignee:

SOFTWARE AG, Darmstadt, DE;

Attorney:
Primary Examiner:
Int. Cl.
CPC ...
H04L 29/08 (2006.01); H04L 29/06 (2006.01); H04L 29/12 (2006.01); G06F 16/955 (2019.01); H04L 12/66 (2006.01);
U.S. Cl.
CPC ...
H04L 67/40 (2013.01); G06F 16/955 (2019.01); H04L 12/66 (2013.01); H04L 61/2517 (2013.01); H04L 67/16 (2013.01); H04L 67/327 (2013.01);
Abstract

Certain example embodiments relate to service mesh management. A service mesh proxy routes incoming requests to one or more microservices in a container. At least one microservice has one or more associated API twins, each definable to enforce a policy based on application-level context information unavailable from incoming requests. A microgateway hosting the API twin(s) is instantiated and is configurable to automatically and transparently ensure that (a) incoming requests that otherwise would be directed to an end microservice having one or more associated API twins will be re-directed to an appropriate one of these one or more API twins en route to the end microservice, and (b) outgoing responses that otherwise would be directed by each such end microservice to the service mesh proxy will be re-routed to the microgateway en route to the service mesh proxy. Incoming requests' structures are unchanged pre- and post-microgateway runtime.


Find Patent Forward Citations

Loading…