Serverless application operational recovery and manifest creation
AssigneeEMC IP Holding Company LLC
InventorsAssaf Natanzon, Amit Lieberman
Life of this patent
Estimating the term…
Abstract
Systems and methods for backing up and restoring serverless applications are provided. A serverless application is queried to identify the functions and services used. These functions and services are transformed into a manifest or graph that allows the relationships of the serverless application to be identified in an automated manner. The serverless application can be backed up and/or restored using the manifest.
Claims18
A method for backing up a serverless application, the serverless application including backend services, application functions, and function mappings, the method comprising:
- adding function vertices and service vertices to a manifest, wherein each function vertex corresponds to a function of the serverless application and each service vertex corresponds to a backend service;
- identifying characteristics of each function;
- adding the identified characteristics to the manifest as edges between the function vertices and the service vertices;
- evaluating the manifest to identify components of the serverless application that impact a persistent state, wherein the function vertices and the service vertices that are not connected to other function vertices or service vertices by an edge are not included in the serverless application and do not impact the persistent state;
- and
- backing up the identified components as a single serverless application, wherein the function vertices and the service vertices that do not impact the persistent state of the identified components are backed up as a different serverless application.
A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
- adding function vertices and service vertices to a manifest, wherein each function vertex corresponds to a function of the serverless application and each service vertex corresponds to a backend service;
- identifying characteristics of each function;
- adding the identified characteristics to the manifest as edges between the function vertices and the service vertices;
- evaluating the manifest to identify components of the serverless application that impact a persistent state, wherein the function vertices and the service vertices that are not connected to other function vertices or service vertices by an edge are not included in the serverless application and do not impact the persistent state;
- and
- backing up the identified components as a single serverless application, wherein the function vertices and the service vertices that do not impact the persistent state of the identified components are backed up as a different serverless application.
Dependencies are inferred from the claim text.