Managing and executing serverless function command sets in a messaging service
A serverless function execution system enables fast, efficient and flexible deployment and execution of serverless functions. User commands are received from external messaging systems that cause functions to be executed. A serverless function associated with the user command is determined and the serverless function is executed in an isolation container at a function computation server. A response from the execution of the serverless function is sent to the external messaging system.
1. A method, comprising:
receiving, at a messaging server, a user textual message, the user textual message comprised of a command prefix and one or more subcommands;
determining an API endpoint associated with a first subcommand of the one or more subcommands and the command prefix;
routing one or more parameters from the user textual message to the API endpoint;
receiving the one or more parameters at the API endpoint;
executing a serverless function within an isolation container in response to the received one or more parameters by executing function code using one or more associated function source code locations;
returning a result of the execution of the serverless function to the messaging server.
2. The method as recited in claim 1 , further comprising:
retrieving the function code by referring to an app definition associated with the user textual message;
selecting a compute server based on the user textual message;
causing the selected compute server to execute the function code.
3. The method as recited in claim 2 , further comprising:
storing a plurality of app definitions;
wherein each app definition includes a mapping of user textual message subcommands to function code.
4. The method as recited in claim 2 , wherein an app is associated with a user textual message command prefix.
5. The method as recited in claim 1 , wherein an app is associated with a user textual message command prefix, and wherein an app is comprised of one or more subcommands.
6. The method as recited in claim 1 , wherein an app is associated with a user textual message command prefix, wherein an app is comprised of one or more subcommands, and wherein each of the one or more subcommands is mapped to one or more functions.
7. The method as recited in claim 1 , further comprising:
storing a history of functions that were executed by users and identities of the users.
8. One or more non-transitory computer-readable storage media, storing one or more sequences of instructions, which when executed by one or more processors cause performance of:
receiving, at a messaging server, a user textual message, the user textual message comprised of a command prefix and one or more subcommands;
determining an API endpoint associated with a first subcommand of the one or more subcommands and the command prefix;
routing one or more parameters from the user textual message to the API endpoint;
receiving the one or more parameters at the API endpoint;
executing a serverless function within an isolation container in response to the received one or more parameters by executing function code using one or more associated function source code locations;
returning a result of the execution of the serverless function to the messaging server.
9. The one or more non-transitory computer-readable storage media as recited in claim 8 , further comprising:
retrieving the function code by referring to an app definition associated with the user textual message;
selecting a compute server based on the user textual message;
causing the selected compute server to execute the function code.
10. The one or more non-transitory computer-readable storage media as recited in claim 9 , further comprising:
storing a plurality of app definitions;
wherein each app definition includes a mapping of user textual message subcommands to function code.
11. The one or more non-transitory computer-readable storage media as recited in claim 9 , wherein an app is associated with a user textual message command prefix.
12. The one or more non-transitory computer-readable storage media as recited in claim 8 , wherein an app is associated with a user textual message command prefix, and wherein an app is comprised of one or more subcommands.
13. The one or more non-transitory computer-readable storage media as recited in claim 8 , wherein an app is associated with a user textual message command prefix, wherein an app is comprised of one or more subcommands, and wherein each of the one or more subcommands is mapped to one or more functions.
14. The one or more non-transitory computer-readable storage media as recited in claim 8 , further comprising:
storing a history of functions that were executed by users and identities of the users.
15. A system, comprising:
a messaging server, implemented at least partially in hardware, configured to:
receive a user textual message, the user textual message comprised of a command prefix and one or more subcommands;
determine an API endpoint associated with a first subcommand of the one or more subcommands and the command prefix; and
route one or more parameters from the user textual message to the API endpoint;
a function computation system, implemented at least partially in hardware, configured to:
receive the one or more parameters at the API endpoint;
execute a serverless function within an isolation container in response to the received one or more parameters by executing function code using one or more associated function source code locations; and
return a result of the execution of the serverless function to the messaging server.
16. The system as recited in claim 15 , wherein the function computation system is further configured to:
retrieve the function code by referring to an app definition associated with the user textual message;
select a compute server based on the user textual message;
cause the selected compute server to execute the function code.
17. The system as recited in claim 16 , wherein the messaging server is further configured to:
store a plurality of app definitions;
wherein each app definition includes a mapping of user textual message subcommands to function code.
18. The system as recited in claim 16 , wherein an app is associated with a user textual message command prefix.
19. The system as recited in claim 15 , wherein an app is associated with a user textual message command prefix, and wherein an app is comprised of one or more subcommands.
20. The system as recited in claim 15 , wherein an app is associated with a user textual message command prefix, wherein an app is comprised of one or more subcommands, and wherein each of the one or more subcommands is mapped to one or more functions.