18541245. DYNAMIC APPLICATION PROGRAMMING INTERFACE (API) CONTRACT GENERATION AND CONVERSION THROUGH MICROSERVICE SIDECARS simplified abstract (Intel Corporation)
Contents
- 1 DYNAMIC APPLICATION PROGRAMMING INTERFACE (API) CONTRACT GENERATION AND CONVERSION THROUGH MICROSERVICE SIDECARS
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 DYNAMIC APPLICATION PROGRAMMING INTERFACE (API) CONTRACT GENERATION AND CONVERSION THROUGH MICROSERVICE SIDECARS - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
DYNAMIC APPLICATION PROGRAMMING INTERFACE (API) CONTRACT GENERATION AND CONVERSION THROUGH MICROSERVICE SIDECARS
Organization Name
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 18541245 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 a first API exposed by a destination microservice, which uses a different API technology. A second contract is then dynamically generated based on the first contract, specifying an intermediate API that utilizes the selected API technology. A second sidecar of the destination microservice generates the intermediate API and connects it to the first API.
- Use of sidecars for dynamic API contract generation and conversion
- Intercepting calls to APIs with different technologies
- Dynamically generating contracts for intermediate APIs
- Connecting intermediate APIs to existing APIs
Potential Applications
This technology could be applied in:
- Microservices architecture
- API management systems
- Service mesh environments
Problems Solved
This technology helps to:
- Facilitate communication between microservices with different API technologies
- Streamline API contract generation and conversion processes
- Enhance interoperability in complex IT environments
Benefits
The benefits of this technology include:
- Improved flexibility in API integration
- Simplified management of diverse API technologies
- Enhanced scalability and adaptability in microservices architectures
Potential Commercial Applications
Potential commercial applications of this technology include:
- Cloud service providers
- Enterprise software companies
- API management platforms
Possible Prior Art
One possible prior art for this technology is the use of API gateways for API management and transformation in microservices architectures.
Unanswered Questions
How does this technology impact the performance of microservices architectures?
This article does not delve into the potential performance implications of using sidecars for dynamic API contract generation and conversion. Further research is needed to understand how this technology may affect the overall performance of microservices architectures.
What security measures are in place to protect the generated intermediate APIs?
The article does not address the security aspects of the generated intermediate APIs. It would be beneficial to explore the security measures implemented to safeguard these APIs from potential threats and vulnerabilities.
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.