# US 2022/0012111 A1 · Api registry in a container platform for automatically generating client code libraries

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0012111 A1
- Document ID: US20220012111A1
- Status: Published application
- Kind: A1
- Application number: 17/485,689
- Filed: 2021-09-27
- Published: 2022-01-13
- Earliest claimed: 2017-09-30
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Claudio Caldato; Boris Scholl
- Web page: https://patentgrep.com/patent/US20220012111A1

## CPC

- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 8/60: Software deployment
- G06F 9/455: Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 9/505: {considering the load}
- G06F 9/5072: {Grid computing}
- G06F 9/5083: {Techniques for rebalancing the load in a distributed system}
- G06F 11/203: {using migration}
- G06F 11/362: Debugging of software
- G06F 11/3644: {by instrumenting at runtime}
- G06F 21/602: {Providing cryptographic facilities or services}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- G06F 3/0482: Interaction with lists of selectable items, e.g. menus
- G06F 8/63: {Image based installation; Cloning; Build to order}
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 2009/45562: {Creating, deleting, cloning virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method of providing Application Programming Interface (API) functions for registered service endpoints in container environments may include receiving, at an API registry, a request from a second service to use a first service in a container environment, where the API registry may list one or more API functions that call the first service. The method may also include generating, by the API registry, a client library for the second service that includes the one or more API functions to execute calls from the second service to the first service in the container environment.

## Claims

### Claim 1

A method of providing Application Programming Interface (API) functions for registered service endpoints in container environments, the method comprising:
receiving, at an API registry, a request from a second service to use a first service in a container environment, wherein the API registry lists one or more API functions that call the first service; and
generating, by the API registry, a client library for the second service that includes the one or more API functions to execute calls from the second service to the first service in the container environment.

### Claim 2 (depends on 1)

The method of claim 1, wherein the method further comprises:
receiving, at the API registry, a request from the one or more API functions for an endpoint of the first service; and
providing, by the API registry, the endpoint of the first service such that the one or more API functions in the second service can execute a call to the endpoint of the first service in the container environment.

### Claim 3 (depends on 1)

The method of claim 1, wherein the request from the second service to use the first service is received in a development environment.

### Claim 4 (depends on 2)

The method of claim 2, wherein the request from the one or more API functions for the endpoint of the first service is received in a production environment.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
receiving, at the API registry, an API definition comprising:
an endpoint of the first service that is encapsulated in a container that is deployed in the container environment; and
the one or more API functions;
creating, by the API registry, a binding between the one or more API functions and the endpoint of the first service.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
after providing the client library to the second service, receiving an change to the endpoint of the first service; and
before receiving a request from the one or more API functions, creating a new binding between the first service and the endpoint after the change to the endpoint.

### Claim 7 (depends on 1)

The method of claim 1, wherein the client library comprises an object class with member functions that implement the API functions.

### Claim 8 (depends on 1)

The method of claim 1, wherein the client library comprises a direct call to the endpoint of the first service.

### Claim 9 (depends on 1)

The method of claim 1, wherein the client library reformats data received as one or more parameters of the one or more API functions into an HTTP call to the endpoint of the first service.

### Claim 10 (depends on 9)

The method of claim 9, wherein the client library requests additional information from a third service to add to the HTTP call of the endpoint of the first service.

### Claim 11 (depends on 1)

The method of claim 1, wherein the client library comprises code that retries unsuccessful calls to the first service.

### Claim 12 (depends on 1)

The method of claim 1, wherein the client library comprises code that extracts a result value from a result set of the first service, and packages the result value as a return value for the one or more API functions.

### Claim 13

A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, causes the one or more processors to perform operations comprising:
receiving, at an API registry, a request from a second service to use a first service in a container environment, wherein the API registry lists one or more API functions that call the first service; and
generating, by the API registry, a client library for the second service that includes the one or more API functions to execute calls from the second service to the first service in the container environment.

### Claim 14 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein an endpoint of the first service comprises:
an IP address; and
a port number.

### Claim 15 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the container environment comprises a plurality of services encapsulated in containers.

### Claim 16 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the API registry is deployed as a service encapsulated in a container in the container environment.

### Claim 17 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the operations further comprise:
identifying, by the API registry, any available endpoints for containerized services that have been deployed to the container environment.

### Claim 18

A system comprising:
one or more processors; and
one or more memory devices comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
receiving, at an API registry, a request from a second service to use a first service in a container environment, wherein the API registry lists one or more API functions that call the first service; and
generating, by the API registry, a client library for the second service that includes the one or more API functions to execute calls from the second service to the first service in the container environment.

### Claim 19 (depends on 18)

The system of claim 18, wherein the operations further comprise:
causing a list of API functions for all services registered with the API registry to be displayed in a user interface.

### Claim 20 (depends on 19)

The system of claim 19, wherein the request from the second service to use the first service is received by receiving a selection of one of the one or more API functions displayed in the user interface.
