IP Library › Granted Patent US 12693902

Granted Patent B2

US 12693902 · App. 18/324,639 · Granted Jul 28, 2026

Self destruction of microservices

Inventors: Govinda Rajulu Nelluri (Hyderabad, IN); Udaya Ramu Peethani (Hyderabad, IN); Narasimha M. Edala (Hyderabad, IN)

Assignee: Wells Fargo Bank, N.A.

G06F9/5033 G06F16/951

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 12693902
App. No.: 18/324,639
Granted: Jul 28, 2026
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

This disclosure describes techniques that include eliminating duplicative microservices and/or consolidating microservices, thereby reducing the number of microservices being used, and enabling a more efficient use of resources consumed by microservices. The techniques include obtaining, by a computing system, data about a plurality of microservices that are available to provide services on a network, identifying, based on usage statistics, a legacy microservice to be decommissioned, wherein the legacy microservice is included in the plurality of microservices available to provide services on the network, and wherein making the legacy microservice available on the network consumes resources on the network, configuring the legacy microservice to be capable of deallocating the resources consumed on the network; routing requests intended for the legacy microservice to another microservice, and after routing requests intended for the legacy microservice to the other microservice, enabling the legacy microservice to deallocate the resources.

Claims (60)

1 . A method comprising:

obtaining, by a computing system, usage statistics indicating traffic to a plurality of microservices that are available to provide services on a network;

identifying, by the computing system and based on the usage statistics, a legacy microservice to be decommissioned, wherein the legacy microservice is included in the plurality of microservices available to provide services on the network, and wherein making the legacy microservice available on the network consumes resources on the network;

configuring the legacy microservice, by the computing system, to be capable of deallocating the resources consumed on the network;

routing, by the computing system, requests intended for the legacy microservice to a stand-in microservice;

after routing requests intended for the legacy microservice to the stand-in microservice, enabling, by the computing system, the legacy microservice to deallocate the resources;

routing, by the computing system, requests intended for the stand-in microservice to a replacement microservice; and

after routing the requests intended for the stand-in microservice to the replacement microservice, deallocating, by the computing system, the stand-in microservice.

2 . The method of claim 1 , wherein obtaining the usage statistics includes:

crawling the network to obtain the usage statistics.

3 . The method of claim 1 , wherein identifying the legacy microservice includes:

identifying, based on traffic patterns in the network, a replacement microservice that is available to replace the legacy microservice.

4 . The method of claim 3 , wherein identifying the replacement microservice includes:

determining that traffic processed by the replacement microservice exceeds a threshold.

5 . The method of claim 3 , wherein identifying the replacement microservice includes:

determining that the replacement microservice provides at least some functionality of the legacy microservice.

6 . The method of claim 3 , wherein identifying the replacement microservice includes:

determining that traffic to the replacement microservice exceeds traffic to another microservice that performs functions similar to the legacy microservice.

7 . The method of claim 1 , wherein routing requests intended for the legacy microservice to the stand-in microservice includes:

initializing, by the computing system, the stand-in microservice.

8 . The method of claim 7 , the method further comprising:

evaluating, by the computing system, whether the stand-in microservice can replace the legacy microservice.

9 . The method of claim 7 , wherein the stand-in microservice consumes additional resources on the network, and wherein the method further comprises:

configuring the stand-in microservice, by the computing system, to be capable of deallocating the additional resources.

10 . The method of claim 9 , wherein initializing the stand-in microservice includes:

initializing a microservice based on the replacement microservice.

11 . The method of claim 1 , wherein configuring the legacy microservice to be capable of deallocating the resources consumed on the network includes:

configuring the legacy microservice through inversion of control.

12 . The method of claim 1 , wherein configuring the legacy microservice to be capable of deallocating the resources consumed on the network includes:

configuring the legacy microservice through a plug-in configured to execute within a container hosting the legacy microservice, wherein the plug-in is self-appointed to execute within the container.

13 . The method of claim 12 , wherein configuring the legacy microservice to be capable of deallocating the resources consumed on the network further includes:

enabling the plug-in to instantiate a counter; and

configuring the legacy microservice through a plug-in configured to execute within a container hosting the legacy microservice.

14 . A computing system comprising a memory device and processing circuitry having access to the memory device, wherein the processing circuitry is configured to:

obtain usage statistics indicating traffic to a plurality of that are available to provide services on a network;

identify based on the usage statistics, a legacy microservice to be decommissioned, wherein the legacy microservice is included in the plurality of microservices available to provide services on the network, and wherein making the legacy microservice available on the network consumes resources on the network;

configure the legacy microservice to be capable of deallocating the resources consumed on the network;

route requests intended for the legacy microservice to a stand-in microservice;

after routing requests intended for the legacy microservice to the stand-in microservice, enable the legacy microservice to deallocate the resources;

route requests intended for the stand-in microservice to a replacement microservice; and

deallocate, after routing the requests intended for the stand-in microservice to the replacement microservice, the stand-in microservice.

15 . The computing system of claim 14 , wherein to obtain the usage statistics, the processing circuitry is further configured to:

crawl the network to obtain the usage statistics.

16 . The computing system of claim 14 , wherein to route requests intended for the legacy microservice to the stand-in microservice, the processing circuitry is further configured to:

initialize the stand-in microservice.

17 . The computing system of claim 16 , wherein the stand-in microservice consumes additional resources on the network, and wherein the processing circuitry is further configured to:

configure the stand-in microservice to be capable of deallocating the additional resources.

18 . The computing system of claim 14 , wherein to configure the legacy microservice to be capable of deallocating the resources consumed on the network, the processing circuitry is further configured to:

configure the legacy microservice through a plug-in configured to execute within a container hosting the legacy microservice, wherein the plug-in is self-appointed to execute within the container.

19 . The computing system of claim 18 , wherein to configure the legacy microservice to be capable of deallocating the resources consumed on the network, the processing circuitry is further configured to:

enable the plug-in to instantiate a counter; and

configure the legacy microservice through a plug-in configured to execute within a container hosting the legacy microservice.