Operational recovery of serverless applications in a cloud-based compute services platform

1. An apparatus comprising:

at least one processing platform comprising a plurality of processing devices;

said at least one processing platform being configured:

to receive a request to execute a serverless application;

to initiate execution of the serverless application responsive to the request;

to utilize one or more application function mappings to invoke one or more application functions with each such application function interacting with one or more backend services in executing the serverless application;

to capture state of the serverless application for a particular point in time; and

to perform operational recovery of the serverless application for the particular point in time utilizing the captured state;

wherein capturing state of the serverless application for the particular point in time comprises capturing the state in accordance with a previously-generated serverless application manifest that comprises:

the one or more application function mappings;

container image identifiers for respective ones of the application functions; and

descriptors for respective ones of the one or more backend services;

wherein the serverless application manifest is automatically generated in conjunction with execution of the serverless application.

2. The apparatus of claim 1 wherein the request initiating execution of the given serverless application is received in an application programming interface gateway of the processing platform from a user device over a network.

3. The apparatus of claim 1 wherein the application functions each execute in one or more stateless ephemeral containers of the processing platform.

4. The apparatus of claim 1 wherein the backend services comprise at least one of a database service, an object storage service and a message processing service.

5. The apparatus of claim 1 wherein the one or more application function mappings each specify one or more conditions under which particular ones of the application functions are invoked.

6. The apparatus of claim 5 wherein the conditions specified by the one or more application function mappings comprise respective events each relating to one or more of the backend services.

7. The apparatus of claim 1 wherein the serverless application manifest further comprises for each of the one or more application functions of the serverless application:

a version indicator for the corresponding container image;

instructions for obtaining corresponding application function binaries or associated code; and

one or more bindings of the application function to respective ones of the backend services with which the application function interacts.

8. The apparatus of claim 7 wherein the instructions for obtaining corresponding application function binaries or associated code comprise instructions for downloading one or more of the application function binaries or associated code from a container registry or code hub.

9. The apparatus of claim 1 wherein the processing platform comprises a serverless application backup orchestrator configured to capture state of the serverless application and to perform operational recovery of the serverless application.

10. The apparatus of claim 1 wherein the processing platform in capturing the state of the serverless application for the particular point in time is further configured:

to store metadata for the one or more application function mappings that are part of the serverless application manifest;

to store a copy of a current binary or associated code for each application function container image identified in the serverless application manifest;

to generate backups for each backend service having a descriptor in the serverless application manifest; and

to generate additional metadata combining the metadata for the one or more application function mappings, the one or more stored copies of the current binaries or associated code, and the backups of the one or more backend services, into a serverless application backup for the particular point in time.

11. The apparatus of claim 10 wherein the processing platform in performing operational recovery of the serverless application for the particular point in time utilizing the captured state is further configured:

to obtain the serverless application backup for the particular point in time;

to update the one or more application function mappings based at least in part on the stored metadata;

to redeploy the application function container images from respective stored copies of their current binaries or associated code;

to recover the backend services from their respective backups; and

to execute the serverless application utilizing the updated one or more application function mappings, the redeployed application function container images and the recovered backend services.

12. The apparatus of claim 1 wherein the processing platform is further configured:

to capture state of application functions and backend services data of the serverless application at each of a plurality of different points in time in accordance with the previously-generated serverless application manifest;

to permit user selection of at least one of a plurality of serverless application backups characterizing the captured state for respective ones of the points in time; and

to recover the serverless application using the selected at least one of the serverless application backups;

wherein the user is permitted to select a first one of the serverless application backups for recovering the application functions and a second one of the serverless application backups different than the first serverless application backup for recovering the backend services data;

the application functions and the backend services data of the serverless application thereby being separately recoverable from different ones of the serverless application backups corresponding to respective different points in time.

13. The apparatus of claim 1 wherein initiating execution of the serverless application responsive to the request comprises initiating execution of the serverless application based at least in part on the server application manifest.

14. A method comprising:

receiving a request to execute a serverless application;

initiating execution of the serverless application responsive to the request;

utilizing one or more application function mappings to invoke one or more application functions with each such application function interacting with one or more backend services in executing the serverless application;

capturing state of the serverless application for a particular point in time; and

performing operational recovery of the serverless application for the particular point in time utilizing the captured state;

wherein capturing state of the serverless application for the particular point in time comprises capturing the state in accordance with a previously-generated serverless application manifest that comprises:

the one or more application function mappings;

container image identifiers for respective one of the application functions; and

descriptors for respective ones of the one or more backend services;

wherein the serverless application manifest is automatically generated in conjunction with execution of the serverless application; and

wherein the method is performed by at least one processing platform comprising a plurality of processing devices.

15. The method of claim 14 wherein capturing the state of the serverless application for the particular point in time further comprises:

storing metadata for the one or more application function mappings that are part of the serverless application manifest;

storing a copy of a current binary or associated code for each application function container image identified in the serverless application manifest;

generating backups for each backend service having a descriptor in the serverless application manifest; and

generating additional metadata combining the metadata for the one or more application function mappings, the one or more stored copies of the current binaries or associated code, and the backups of the one or more backend services, into a serverless application backup for the particular point in time.

16. The method of claim 15 wherein performing operational recovery of the serverless application for the particular point in time utilizing the captured state further comprises:

obtaining the serverless application backup for the particular point in time;

updating the one or more application function mappings based at least in part on the stored metadata;

redeploying the application function container images from respective stored copies of their current binaries or associated code;

recovering the backend services from their respective backups; and

executing the serverless application utilizing the updated one or more application function mappings, the redeployed application function container images and the recovered backend services.

17. The method of claim 14 wherein the one or more application function mappings each specify one or more conditions under which particular ones of the application functions are invoked.

18. A computer program product comprising a non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing platform causes said at least one processing platform:

to receive a request to execute a serverless application;

to initiate execution of the serverless application responsive to the request;

to utilize one or more application function mappings to invoke one or more application functions with each such application function interacting with one or more backend services in executing the serverless application;

to capture state of the serverless application for a particular point in time; and

to perform operational recovery of the serverless application for the particular point in time utilizing the captured state;

wherein capturing state of the serverless application for the particular point in time comprises capturing the state in accordance with a previously-generated serverless application manifest that comprises:

the one or more application function mappings;

container image identifiers for respective one of the application functions; and

descriptors for respective ones of the one or more backend services;

wherein the serverless application manifest is automatically generated in conjunction with execution of the serverless application.

19. The computer program product of claim 18 wherein the processing platform in capturing the state of the serverless application for the particular point in time is further configured:

to store metadata for the one or more application function mappings that are part of the serverless application manifest;

to store a copy of a current binary or associated code for each application function container image identified in the serverless application manifest;

to generate backups for each backend service having a descriptor in the serverless application manifest; and

to generate additional metadata combining the metadata for the one or more application function mappings, the one or more stored copies of the current binaries or associated code, and the backups of the one or more backend services, into a serverless application backup for the particular point in time.

20. The computer program product of claim 19 wherein the processing platform in performing operational recovery of the serverless application for the particular point in time utilizing the captured state is further configured:

to obtain the serverless application backup for the particular point in time;

to update the one or more application function mappings based at least in part on the stored metadata;

to redeploy the application function container images from respective stored copies of their current binaries or associated code;

to recover the backend services from their respective backups; and

to execute the serverless application utilizing the updated one or more application function mappings, the redeployed application function container images and the recovered backend services.