Intel corporation (20240111615). DYNAMIC APPLICATION PROGRAMMING INTERFACE (API) CONTRACT GENERATION AND CONVERSION THROUGH MICROSERVICE SIDECARS simplified abstract

DYNAMIC APPLICATION PROGRAMMING INTERFACE (API) CONTRACT GENERATION AND CONVERSION THROUGH MICROSERVICE SIDECARS

Organization Name

intel corporation

Inventor(s)

Marcos Carranza of Portland OR (US)

Cesar Martinez-spessot of Hillsboro OR (US)

Mateo Guzman of Beaverton OR (US)

Francesc Guim Bernat of Barcelona (ES)

Karthik Kumar of Chandler AZ (US)

Rajesh Poornachandran of Portland OR (US)

Kshitij Arun Doshi of Tempe AZ (US)

DYNAMIC APPLICATION PROGRAMMING INTERFACE (API) CONTRACT GENERATION AND CONVERSION THROUGH MICROSERVICE SIDECARS - A simplified explanation of the abstract

This abstract first appeared for US patent application 20240111615 titled 'DYNAMIC APPLICATION PROGRAMMING INTERFACE (API) CONTRACT GENERATION AND CONVERSION THROUGH MICROSERVICE SIDECARS

Simplified Explanation

Embodiments described herein involve the use of sidecars for dynamic API contract generation and conversion. In a scenario, a first sidecar of a source microservice intercepts a call to an API exposed by a destination microservice. The call uses a specific API technology defined by a contract and is initiated by the source microservice. A different API technology is selected from multiple options, leading to the dynamic generation of an intermediate API contract by the first sidecar. A second sidecar of the destination microservice then generates the intermediate API and connects it to the original API.

• Sidecars used for dynamic API contract generation and conversion
• First sidecar intercepts calls to destination microservice APIs
• Selection of different API technology triggers dynamic contract generation
• Second sidecar generates and connects intermediate API

Potential Applications

This technology can be applied in software development, microservices architecture, API management, and system integration.

Problems Solved

This technology solves the challenge of integrating microservices with different API technologies seamlessly and dynamically generating contracts for communication between services.

Benefits

The benefits of this technology include improved flexibility, scalability, and efficiency in managing API contracts and communication between microservices.

Potential Commercial Applications

Potential commercial applications include API management platforms, microservices development tools, and system integration solutions.

Possible Prior Art

One possible prior art could be the use of API gateways for managing API communication between microservices in a similar manner.

How does this technology impact the performance of microservices architecture?

This article does not delve into the specific performance implications of using sidecars for dynamic API contract generation and conversion. Further research or testing may be needed to determine the performance impact on microservices systems.

What are the security considerations when using sidecars for API contract generation?

The article does not address the security aspects of using sidecars for API contract generation. It would be essential to explore potential security vulnerabilities and best practices for securing communication between microservices in this context.

Original Abstract Submitted

embodiments described herein are generally directed to the use of sidecars to perform dynamic api contract generation and conversion. in an example, a first sidecar of a source microservice intercepts a first call to a first api exposed by a destination microservice. the first call makes use of a first api technology specified by a first contract and is originated by the source microservice. an api technology is selected from multiple api technologies. the selected api technology is determined to be different than the first api technology. based on the first contract, a second contract is dynamically generated that specifies an intermediate api that makes use of the selected api technology. a second sidecar of the destination microservice is caused to generate the intermediate api and connect the intermediate api to the first api.