18077753. SECURE EXECUTION OF MICROSERVICES simplified abstract (Dell Products L.P.)
Contents
- 1 SECURE EXECUTION OF MICROSERVICES
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 SECURE EXECUTION OF MICROSERVICES - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Commercial Applications
- 1.9 Prior Art
- 1.10 Frequently Updated Research
- 1.11 Questions about Secure Microservice Execution Technology
- 1.12 Original Abstract Submitted
SECURE EXECUTION OF MICROSERVICES
Organization Name
Inventor(s)
Teja Madhukar Manakame of Bangalore (IN)
Shibi Panikkar of Bangalore (IN)
Jennifer Ann Felch of Austin TX (US)
SECURE EXECUTION OF MICROSERVICES - A simplified explanation of the abstract
This abstract first appeared for US patent application 18077753 titled 'SECURE EXECUTION OF MICROSERVICES
Simplified Explanation
This patent application describes methods, apparatus, and storage media for securely executing microservices in a microservice architecture. It involves generating session identifiers, identifying execution plans, maintaining data structures to track execution order, and preventing execution of microservices if the order does not match the specified order.
- Securely executing microservices in a microservice architecture
- Generating session identifiers for requests
- Identifying execution plans based on plan identifiers
- Maintaining data structures to track execution order
- Preventing execution of microservices if the order does not match the specified order
Potential Applications
This technology can be applied in various industries where secure execution of microservices is crucial, such as finance, healthcare, and e-commerce.
Problems Solved
This technology addresses the problem of ensuring the secure and accurate execution of microservices in a specified order within a microservice architecture.
Benefits
The benefits of this technology include enhanced security, improved reliability of microservice execution, and better control over the order of execution.
Commercial Applications
Title: Secure Microservice Execution Technology This technology can be commercially used in cloud computing platforms, enterprise software systems, and any application that relies on microservices for its functionality.
Prior Art
Readers can explore prior art related to secure microservice execution, session management, and execution order tracking in microservice architectures.
Frequently Updated Research
Stay updated on the latest research developments in secure microservice execution, session management techniques, and optimization of microservice architectures.
Questions about Secure Microservice Execution Technology
How does this technology improve the security of microservice execution?
This technology enhances security by tracking and enforcing the specified order of microservice execution, preventing unauthorized access or disruptions.
What are the key features of this technology that set it apart from existing solutions?
The key features include session-based identification, execution plan tracking, and prevention of out-of-order execution, ensuring secure and reliable microservice operation.
Original Abstract Submitted
Methods, apparatus, and processor-readable storage media for securely executing microservices are described herein. An example computer-implemented method includes: generating a session identifier for a request associated with executing one or more microservices in a microservice architecture; identifying an execution plan for the request based at least in part on a plan identifier specified for a first one of the microservices, wherein the execution plan indicates a specified order for executing the microservices for the request; maintaining a set of chained data structures to track an execution order of the microservices based on the session identifier; detecting, based at least in part on the set of chained data structures, that the execution order of the identified execution plan does not match the specified order for at least a given one of the of the one or more microservices; and in response to the detecting, preventing at least the given microservice from being executed.
