# US 2021/0240540 A1 · Serverless platform request routing > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0240540 A1 - Document ID: US20210240540A1 - Status: Published application - Kind: A1 - Application number: 16/780,654 - Filed: 2020-02-03 - Published: 2021-08-05 - Earliest claimed: 2020-02-03 - Assignees: International Business Machines Corporation - Applicants: International Business Machines Corporation - Inventors: Yue Wang; Yue Chen; Wei ming He; Huai Nan Zhou; Hui Gao; Yanfeng Shi; Hai Jun Xu; Wen Tao Zhang - Web page: https://patentgrep.com/patent/US20210240540A1 ## CPC - G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)} - G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files} - G06F 9/45558: {Hypervisor-specific management and integration aspects} - G06F 9/54: Interprogram communication - G06F 16/2474: {Sequence data queries, e.g. querying versioned data} - G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Routing containerized services requests on a serverless platform can include responding to receiving on the serverless platform a request for a containerized service and detecting a potential request failure. The response to the potential request failure can include searching a database that maps version-specific requests to a plurality of containers that are configured and managed by the serverless platform. The routing can include redirecting the request to a container containing a prior version of the containerized service requested in response to determining that the prior version of the containerized service maps to a version-specific request that matches the request received. ## Claims ### Claim 1 A method, comprising: responsive to receiving on a serverless platform a request for a containerized service and detecting a potential request failure, searching a database with computer hardware, the database mapping version-specific requests to a plurality of containers configured and managed by the serverless platform; and redirecting the request to a container containing a prior version of the containerized service requested in response to determining that the container maps to a version-specific request that matches the request received. ### Claim 2 (depends on 1) The method of claim 1, further comprising generating and electronically storing a routing rule that redirects future requests matching the request received to the container containing the prior version of the containerized service. ### Claim 3 (depends on 1) The method of claim 1, wherein the redirecting comprises generating a reconfigured request different from the request received, the reconfigured request corresponding to the container containing the prior version of the containerized service requested. ### Claim 4 (depends on 3) The method of claim 3, wherein the generating comprises adding a revision version indicator to a header of the request in response to failing to invoke the containerized service requested using a latter revision version indicator. ### Claim 5 (depends on 1) The method of claim 1, further comprising adding a path property to a build component of the serverless platform when creating a new version of the containerized service, wherein the path property is used to locate interface definition information for mapping a newly configured request to the new version of the containerized service. ### Claim 6 (depends on 5) The method of claim 5, further comprising extracting the interface definition information from an application programming interface (API) definition file in response to locating the API definition file stored in a repository or extracting the interface definition information from a container launched from a container image. ### Claim 7 (depends on 1) The method of claim 1, wherein the detecting comprises determining that a configuration of the request does not match a configuration specified for a current version of the containerized service. ### Claim 8 A system, comprising: a processor configured to initiate operations including: responsive to receiving on a serverless platform a request for a containerized service and detecting a potential request failure, searching a database with computer hardware, the database mapping version-specific requests to a plurality of containers configured and managed by the serverless platform; and redirecting the request to a container containing a prior version of the containerized service requested in response to determining that the container maps to a version-specific request that matches the request received. ### Claim 9 (depends on 8) The system of claim 8, wherein the processor is configured to initiate operations further comprising generating and electronically storing a routing rule that redirects future requests matching the request received to the container containing the prior version of the containerized service. ### Claim 10 (depends on 8) The system of claim 8, wherein the redirecting comprises generating a reconfigured request different from the request received, the reconfigured request corresponding to the container containing the prior version of the containerized service requested. ### Claim 11 (depends on 10) The system of claim 10, wherein the generating comprises adding a revision version indicator to a header of the request in response to failing to invoke the containerized service requested using a latter revision version indicator and determining that an attempt to redirect the request using the revision version indicator does not exceed a retry limit. ### Claim 12 (depends on 8) The system of claim 8, wherein the processor is configured to initiate operations further comprising adding a path property to a build component of the serverless platform when creating a new version of the containerized service, wherein the path property is used to locate interface definition information for mapping a newly configured request to the new version of the containerized service. ### Claim 13 (depends on 12) The system of claim 12, wherein the processor is configured to initiate operations further comprising extracting the interface definition information from an application programming interface (API) definition file in response to locating the API definition file stored in a repository or extracting the interface definition information from a container launched from a container image. ### Claim 14 A computer program product, the computer program product comprising: one or more non-transitory computer-readable storage media and program instructions collectively stored on the one or more non-transitory computer-readable storage media, the program instructions executable by a processor to cause the processor to initiate operations including: responsive to receiving on a serverless platform a request for a containerized service and detecting a potential request failure, searching a database with computer hardware, the database mapping version-specific requests to a plurality of containers configured and managed by the serverless platform; and redirecting the request to a container containing a prior version of the containerized service requested in response to determining that the container maps to a version-specific request that matches the request received. ### Claim 15 (depends on 14) The computer program product of claim 14, wherein the processor is configured to initiate operations further comprising generating and electronically storing a routing rule that redirects future requests matching the request received to the container containing the prior version of the containerized service. ### Claim 16 (depends on 14) The computer program product of claim 14, wherein the redirecting comprises generating a reconfigured request different from the request received, the reconfigured request corresponding to the container containing the prior version of the containerized service requested. ### Claim 17 (depends on 16) The computer program product of claim 16, wherein the generating comprises adding a revision version indicator to a header of the request in response to failing to invoke the containerized service requested using a latter revision version indicator and determining that an attempt to redirect the request using the revision version indicator does not exceed a retry limit. ### Claim 18 (depends on 14) The computer program product of claim 14, wherein the processor is configured to initiate operations further comprising adding a path property to a build component of the serverless platform when creating a new version of the containerized service, wherein the path property is used to locate interface definition information for mapping a newly configured request to the new version of the containerized service. ### Claim 19 (depends on 18) The computer program product of claim 18, wherein the program instructions are executable by the processor to cause the processor to initiate operations further comprising extracting the interface definition information from an application programming interface (API) definition file in response to locating the API definition file stored in a repository or extracting the interface definition information from a container launched from a container image. ### Claim 20 (depends on 14) The computer program product of claim 14, wherein the detecting comprises determining that a configuration of the request does not match a configuration specified for a current version of the containerized service.