Patent ID: 11153412

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.