IP Library Granted Patent US 12,470,482
Granted Patent B2
US 12,470,482 · App. 18/328,974 · Granted Nov 11, 2025

Smart routing of traffic in a cloud computing environment

Inventors: Jignesh Rangwala (Glen Allen, VA); Soumyajit Ray (Glen Allen, VA); Lee Adcock (Midlothian, VA); Mehulkumar Jayantilal Garnara (Glen Allen, VA); Vamsi Kavuri (Glen Allen, VA); Randall Devitto (Orland Park, IL)
Assignee: Capital One Services, LLC
H04L45/70G06F8/60H04L45/76H04L67/10
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 12,470,482
App. No.
18/328,974
Granted
Nov 11, 2025
Kind
B2
Abstract

In some implementations, a device may obtain a codebase, associated with an application and one or more services of the application, that is deployable via both a first framework of the cloud computing environment and a second framework of the cloud computing environment. The device may receive the traffic associated with the application. The device may monitor one or more metrics associated with the traffic. The device may deploy, based on the one or more metrics, the codebase via the first framework or the second framework in the cloud computing environment. The device may route, based on the one or more metrics, the traffic to the first framework or to the second framework.

Claims (85)

1 . A system for routing traffic in a cloud computing environment that includes a serverless framework and a container-based framework, the system comprising:

one or more memories; and

one or more processors, communicatively coupled to the one or more memories, configured to:

obtain a codebase, associated with an application, that is deployable via both the serverless framework of the cloud computing environment and the container-based framework of the cloud computing environment,

wherein the codebase is deployable via a serverless function associated with the serverless framework and via a container associated with the container-based framework;

receive the traffic associated with the application;

monitor one or more metrics associated with the traffic,

wherein the one or more metrics include at least one of one or more performance metrics associated with the traffic, a time associated with the traffic, or one or more system metrics associated with the cloud computing environment, and

wherein the one or more metrics are associated with a performance threshold;

deploy, based on the one or more metrics and using the codebase, the serverless function or the container in the cloud computing environment; and

route, based on one or more values of the one or more metrics satisfying the performance threshold, the traffic to the serverless function or to the container, wherein the performance threshold is indicated by the codebase.

2 . The system of claim 1 , wherein the one or more processors, to route the traffic, are configured to:

route the traffic to:

the container if the one or more values of the one or more metrics satisfy the performance threshold.

3 . The system of claim 1 , wherein the one or more processors, to monitor the one or more metrics associated with the traffic, are configured to:

predict, using a machine learning model, the one or more metrics based on historical traffic associated with the application.

4 . The system of claim 1 , wherein the one or more processors, to route the traffic, are configured to:

route, based on the one or more metrics, the traffic to the serverless function; and

wherein the one or more processors are further configured to:

cause, based on routing the traffic to the serverless function, a utilization of cloud resources associated with the container in the cloud computing environment to be reduced or stopped.

5 . The system of claim 1 , wherein the one or more processors, to route the traffic, are configured to:

route a first portion of the traffic to the serverless function; and

route a second portion of the traffic to the container,

wherein the first portion and the second portion are based on the one or more metrics.

6 . The system of claim 1 , wherein the one or more system metrics associated with the cloud computing environment include a concurrency limit, and wherein the one or more processors, to route the traffic, are configured to:

route the traffic to the container based on a utilization of the serverless framework indicating that the concurrency limit is met.

7 . The system of claim 1 , wherein the one or more processors are further configured to:

obtain a configuration file associated with the codebase that indicates whether the traffic is to be routed to the serverless function or the container, and

wherein the one or more processors, to route the traffic, are configured to:

route the traffic to the serverless function or the container based on whether the traffic is to be routed to the serverless function or the container.

8 . The system of claim 1 , wherein the one or more performance metrics include at least one of:

a transactions per second (TPS) metric,

a requests per second metric, or

a quantity of users.

9 . The system of claim 1 , wherein the one or more processors, to route the traffic, are configured to:

route the traffic to:

the serverless function if the time associated with the traffic indicates that the traffic is occurring during a first time period, or

the container if the time associated with the traffic indicates that the traffic is occurring during a second time period.

10 . A method for routing traffic in a cloud computing environment, comprising:

obtaining, by a device, a codebase, associated with an application and one or more services of the application, that is deployable via both a first framework of the cloud computing environment and a second framework of the cloud computing environment;

receiving, by the device, the traffic associated with the application;

monitoring, by the device, one or more metrics associated with the traffic,

wherein the one or more metrics are associated with a performance threshold;

determining, by the device and based on the one or more metrics, that the first framework or the second framework is to be used for the traffic;

deploying, by the device and based on the determining, the codebase via the first framework or the second framework in the cloud computing environment; and

routing, based on one or more values of the one or more metrics satisfying the performance threshold, the traffic to the first framework or to the second framework, wherein the performance threshold is indicated by the codebase.

11 . The method of claim 10 , wherein the first framework includes a container-based framework and the second framework includes a serverless framework.

12 . The method of claim 10 , wherein routing the traffic comprises:

routing the traffic to:

the first framework if the one or more values of the one or more metrics satisfy the performance threshold.

13 . The method of claim 10 , wherein routing the traffic comprises:

route, based on the one or more metrics, traffic for respective services of the one or more services to cloud resources associated with the first framework or to the second framework.

14 . The method of claim 10 , wherein routing the traffic comprises:

routing, based on the one or more metrics, the traffic to the first framework, and

the method further comprising:

detecting, based on monitoring the one or more metrics, a change in the one or more values of the one or more metrics;

deploying, based on detecting the change in the one or more values of the one or more metrics, the codebase via the second framework; and

routing, based on detecting the change in the one or more values of the one or more metrics, the traffic to the second framework.

15 . The method of claim 14 , further comprising:

causing, based on routing the traffic to the second framework, a utilization of cloud resources associated with the first framework in the cloud computing environment to be reduced or stopped.

16 . The method of claim 10 , wherein the one or more metrics include at least one of:

a transactions per second (TPS) metric,

a requests per second metric,

a quantity of users,

a timing associated with the traffic, or

one or more system metrics associated with the cloud computing environment.

17 . A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a device, cause the device to:

obtain a codebase, associated with an application, that is deployable via both a serverless framework of a cloud computing environment and a container-based framework of the cloud computing environment,

receive traffic associated with the application;

predict, via a machine learning model, one or more metrics associated with the traffic,

wherein the one or more metrics are associated with a performance threshold;

select, based on the one or more metrics, the serverless framework or the container-based framework for the traffic;

deploy, based on the selecting, a serverless function associated with the serverless framework or a container associated with the container-based framework; and

route, based on one or more values of the one or more metrics satisfying the performance threshold, the traffic to the serverless function or to the container, wherein the performance threshold is indicated by the codebase.

18 . The non-transitory computer-readable medium of claim 17 , wherein the one or more instructions, that cause the device to route the traffic, cause the device to:

route, based on the one or more metrics, the traffic to the serverless function; and

wherein the one or more instructions further cause the device to:

cause, based on routing the traffic to the serverless function, a utilization of cloud resources associated with the container in the cloud computing environment to be reduced or stopped.

19 . The non-transitory computer-readable medium of claim 17 , wherein the one or more instructions, that cause the device to route the traffic, cause the device to:

route a first portion of the traffic to the serverless function; and

route a second portion of the traffic to the container,

wherein the first portion and the second portion are based on the one or more metrics.

20 . The non-transitory computer-readable medium of claim 17 , wherein the one or more metrics include a concurrency limit, and wherein the one or more instructions, that cause the device to route the traffic, cause the device to:

route the traffic to the container based on a utilization of the serverless framework indicating that the concurrency limit is met.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 6, 2023
From: RANGWALA, JIGNESH; RAY, SOUMYAJIT; ADCOCK, LEE; GARNARA, MEHULKUMAR JAYANTILAL; KAVURI, VAMSI; DEVITTO, RANDALL
To: CAPITAL ONE SERVICES, LLC
Reel/Frame 063861/0429 →
Continuity (1)
Related Publication 20240406105A1 · Dec 5, 2024
References Cited (11)
US 11082333B1 · Lam · 2021 [cited by examiner]
US 11256552B1 · Lam · 2022 [cited by examiner]
US 20200213279A1 · Xiong · 2020 [cited by examiner]
US 20210240459A1 · Ranjan · 2021 [cited by examiner]
US 20220158932A1 · Lam · 2022 [cited by examiner]
US 20230100729A1 · Kostic · 2023 [cited by examiner]
US 20230115707A1 · Khan · 2023 [cited by examiner]
US 20230205647A1 · Sharma · 2023 [cited by examiner]
US 20240134835A1 · Creath · 2024 [cited by examiner]
US 20240406105A1 · Rangwala · 2024 [cited by examiner]
WO WO2021197588A1 · 2021 [cited by examiner]